Bug 395630 – crash in Terminal: yum update + service con...

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 395630 - crash in Terminal: yum update + service con...


Summary:	crash in Terminal: yum update + service con...


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:	2007-01-12 00:07 UTC by shivarajan
Modified:	2007-01-12 01:32 UTC

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

Description shivarajan 2007-01-12 00:07:39 UTC

Version: 2.16.0

What were you doing when the application crashed?
yum update + service config.		


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

Memory status: size: 80748544 vsize: 0 resident: 80748544 share: 0 rss: 16752640 rss_rlim: 0
CPU usage: start_time: 1168558039 rtime: 0 utime: 930 stime: 0 cutime:766 cstime: 0 timeout: 164 it_real_value: 0 frequency: 16

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 -1208260912 (LWP 2808)]
[New Thread -1214186608 (LWP 2813)]
(no debugging symbols found)
0x00e56402 in __kernel_vsyscall ()

+ Trace 101429

Thread 1 (Thread -1208260912 (LWP 2808))

#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_valist
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_scrollbar_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#8 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-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_button_box_set_child_size
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_notebook_popup_enable
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_box_pack_start_defaults
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_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_rc_get_module_dir
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#34 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#35 g_main_context_check
from /lib/libglib-2.0.so.0
#36 g_main_loop_run
from /lib/libglib-2.0.so.0
#37 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#38 g_cclosure_marshal_VOID__OBJECT
#39 __libc_start_main
from /lib/libc.so.6
#40 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall

Comment 1 palfrey 2007-01-12 01:32:45 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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