Bug 359854 – crash in Terminal: yum update

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 359854 - crash in Terminal: yum update


Summary:	crash in Terminal: yum update


Status:	RESOLVED DUPLICATE of bug 353498

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-05 11:38 UTC by loic.laurent
Modified:	2006-10-05 12:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description loic.laurent 2006-10-05 11:38:29 UTC

Version: 2.16.0

What were you doing when the application crashed?
yum update


Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 92643328 vsize: 0 resident: 92643328 share: 0 rss: 17223680 rss_rlim: 0
CPU usage: start_time: 1160045879 rtime: 0 utime: 561 stime: 0 cutime:448 cstime: 0 timeout: 113 it_real_value: 0 frequency: 26

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208871216 (LWP 3263)]
[New Thread -1215562864 (LWP 3267)]
(no debugging symbols found)
0x00f62402 in __kernel_vsyscall ()

+ Trace 74661

Thread 1 (Thread -1208871216 (LWP 3263))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_widget_style_get_valist
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_widget_queue_resize
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_notebook_popup_enable
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_rc_get_module_dir
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#30 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#31 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#32 g_main_context_check
from /lib/libglib-2.0.so.0
#33 g_main_loop_run
from /lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 g_cclosure_marshal_VOID__OBJECT
#36 __libc_start_main
from /lib/libc.so.6
#37 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-10-05 12:02:29 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 353498 ***