Bug 120873 – Gnome ternimal does not support man

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 120873 - Gnome ternimal does not support man


Summary:	Gnome ternimal does not support man


Status:	RESOLVED DUPLICATE of bug 96439

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-08-27 21:10 UTC by bogoe
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description bogoe 2003-08-27 21:10:06 UTC

Package: gnome-terminal
Severity: minor
Version: 2.0.1
Synopsis: Gnome ternimal does not support man
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
When using the man application under a gnome terminal it crashed the
terminal.

Steps to reproduce the problem:
1. open a gnome terminal in a remote X-win connection
2. under gnome terminal type "man sed".
3. 

Actual Results:
Just crashed the gnome terminal.

Expected Results:
printout of the man pages for sed.

How often does this happen?
All the times I tryed to read the man for sed.

Additional Information:
I was using a remote connection with X-Win32 for windows.



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...[New Thread 16384 (LWP 14117)]
0x408fa7f7 in waitpid ()
   from /lib/i686/libpthread.so.0

+ Trace 39822

Thread 1 (Thread 16384 (LWP 14117))

#0 waitpid
from /lib/i686/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 __pthread_sighandler
from /lib/i686/libpthread.so.0
#3 <signal handler called>
#4 XftSwapCARD32
from /usr/lib/libXft.so.2
#5 XftSwapImage
from /usr/lib/libXft.so.2
#6 XftGlyphSpecCore
from /usr/lib/libXft.so.2
#7 XftDrawGlyphSpec
from /usr/lib/libXft.so.2
#8 XftDrawCharSpec
from /usr/lib/libXft.so.2
#9 vte_terminal_draw_cells
from /usr/lib/libvte.so.2
#10 vte_terminal_draw_row
from /usr/lib/libvte.so.2
#11 vte_terminal_paint
from /usr/lib/libvte.so.2
#12 vte_terminal_expose
from /usr/lib/libvte.so.2
#13 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 gdk_window_process_updates_internal
from /usr/lib/libgdk-x11-2.0.so.0
#22 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#23 gdk_window_update_idle
from /usr/lib/libgdk-x11-2.0.so.0
#24 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 main
#31 __libc_start_main
from /lib/i686/libc.so.6
#0 waitpid
from /lib/i686/libpthread.so.0





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-27 17:10 -------

The original reporter (bogoe@iol.pt) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-08-28 03:47:38 UTC

Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

*** This bug has been marked as a duplicate of 96439 ***