Bug 107053 – Terminal crashes when typing "man wget"

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 107053 - Terminal crashes when typing "man wget"


Summary:	Terminal crashes when typing "man wget"


Status:	RESOLVED DUPLICATE of bug 104781

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

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Havoc Pennington
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-02-25 18:00 UTC by Keith
Modified:	2004-12-22 21:47 UTC

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

Description Keith 2003-02-25 18:00:15 UTC

Description of Problem:


Steps to reproduce the problem:
1. Open a terminal from the taskbar
2. Type man wget
3. Entire terminal crashes

Actual Results:
Terminal crashes

Expected Results:
See the manpage for wget.

How often does this happen? 
Nearly every time.

Additional Information:
Just applied a recent patch via Redhat's up2date
tool.  Has something to do with the terminal.  I'm
guessing there might be a connection.

Info:
Term: gnome-terminal 2.0.1
OS: Linux ITMNP1 2.4.18-24.8.0 #1 Fri Jan 31
06:51:30 EST 2003 i686 i686 i386 GNU/Linux

Comment 1 John Fleck 2003-02-26 02:10:01 UTC

Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.

Comment 2 Keith 2003-02-26 14:36:50 UTC

Trying to get a stack trace but, my RPM wasn't compiled with 
debugging enabled :(. Any ideas where I can get one?  Or shall I make 
one?

//--- Begin gdb output 
$ gdb gnome-terminal
GNU gdb Red Hat Linux (5.2.1-4)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and 
you are welcome to change it and/or distribute copies of it under 
certain conditions. Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for 
details. This GDB was configured as "i386-redhat-linux"...
(no debugging symbols found)...
(gdb)

Comment 3 Elijah Newren 2003-02-26 16:13:56 UTC

Keith: You don't need debugging symbols to get a stack trace.  The
stack trace is definitely more useful with debugging symbols, but
often times a stack trace without them is enough.

Comment 4 Keith 2003-02-26 16:44:20 UTC

Got it!

//---- Begin GDB output
$ gdb gnome-terminal
GNU gdb Red Hat Linux (5.2.1-4)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and 
you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for 
details.
This GDB was configured as "i386-redhat-linux"...
(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/gnome-terminal 
[New Thread 8192 (LWP 3382)]
Xlib:  extension "RENDER" missing on 
display "localhost.localdomain:2.0".

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8192 (LWP 3382)]
0x40981813 in _XftSmoothGlyphGray565 () from /usr/lib/libXft.so.2
(gdb) thread apply all bt

+ Trace 34312

Thread 1 (Thread 8192 (LWP 3382))

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

Comment 5 Elijah Newren 2003-02-26 16:47:48 UTC

Looks like another duplicate of bug 104781.  I'm going to reopen so I
can mark it as such.

Comment 6 Elijah Newren 2003-02-26 16:49:37 UTC

Okay, marking it as a duplicate.

Keith: Thanks for following up on this!

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