Bug 442311 – crash in Gnome Terminal: Finishing a system upgra...

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 442311 - crash in Gnome Terminal: Finishing a system upgra...


Summary:	crash in Gnome Terminal: Finishing a system upgra...


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-05-30 13:19 UTC by matute
Modified:	2007-06-20 21:29 UTC

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

Description matute 2007-05-30 13:19:44 UTC

Version: 2.16.1

What were you doing when the application crashed?
Finishing a system upgrade


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 224468992 vsize: 224468992 resident: 13512704 share: 11866112 rss: 25378816 rss_rlim: 1793720320
CPU usage: start_time: 1180481440 rtime: 288 utime: 251 stime: 37 cutime:71 cstime: 24 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47866605222208 (LWP 4830)]
[New Thread 1075841344 (LWP 5027)]
(no debugging symbols found)
0x00002b88cdb0bc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 136811

Thread 1 (Thread 47866605222208 (LWP 4830))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_widget_style_get_valist
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#4 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#5 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#6 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#7 gtk_box_pack_start_defaults
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#8 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#9 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#10 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#11 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#12 gtk_notebook_popup_enable
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#13 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#14 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#15 gtk_box_pack_start_defaults
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#16 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#17 gtk_widget_style_get
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#18 gtk_widget_queue_resize
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#19 gtk_widget_set_usize
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#20 gtk_widget_set_usize
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#21 gtk_rc_get_module_dir
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#22 gtk_icon_info_get_type
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#23 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#24 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#25 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#26 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#27 g_cclosure_marshal_VOID__OBJECT
#28 __libc_start_main
from /lib64/libc.so.6
#29 g_cclosure_marshal_VOID__OBJECT
#30 ??
#31 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-06-20 21:29:56 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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