Bug 107731 – man command crashes

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 107731 - man command crashes


Summary:	man command crashes


Status:	RESOLVED DUPLICATE of bug 104781

Product:	vte
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-03-06 15:10 UTC by kdoi
Modified:	2004-12-22 21:47 UTC

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

Description kdoi 2003-03-06 15:10:35 UTC

Package: gnome-terminal
Severity: normal
Version: 2.0.1
Synopsis: man command crashes
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
"man man + return " causes "fatal error".
The terminal get frozen.
This happenes with other man pages,too.


Steps to reproduce the problem:
1. boot the system.
2. launch the terminal window in gnome.
3.type "man man",then press return. 

Actual Results:


Expected Results:


How often does this happen?
always

Additional Information:
It does not happen when I do it in text mode.



Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 1131)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 34579

Thread 1 (Thread 8192 (LWP 1131))

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





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-06 10:10 -------

The original reporter (kdoi@a2.mbn.or.jp) 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, hp@redhat.com.

Comment 1 Havoc Pennington 2003-03-06 15:38:10 UTC

Probably an Xft issue, but you could also try upgrading to latest vte
and gnome-terminal 2.2

Comment 2 Alex Duggan 2003-03-06 18:38:41 UTC


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