GNOME Bugzilla – Bug 398926
Crash in Terminal
Last modified: 2007-03-10 23:30:43 UTC
Version: 2.16.1 What were you doing when the application crashed? i was making an upgrade of my system Distribution: Unknown Gnome Release: 2.16.2 2006-12-29 (GNOME.Org) BugBuddy Version: 2.16.1 System: Linux 2.6.19.2-paldo1 #1 SMP PREEMPT Sat Jan 13 11:29:24 CET 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 218099712 vsize: 218099712 resident: 19279872 share: 8683520 rss: 19279872 rss_rlim: -1 CPU usage: start_time: 1168954641 rtime: 3723 utime: 2911 stime: 812 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 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) 0x00002b76b556b93f in waitpid () from /lib/libpthread.so.0
+ Trace 103936
----------- .xsession-errors --------------------- ** Message: volume = 0 (gnome-terminal:4238): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed (gnome-terminal:4238): GLib-GObject-WARNING **: gsignal.c:2180: invalid object type ` (gnome-terminal:4238): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** (bug-buddy:6987): WARNING **: Couldn't load icon for Open Folder warning: .dynamic section for "/usr/lib/libglib-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgmodule-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgthread-2.0.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***
*** Bug 416637 has been marked as a duplicate of this bug. ***