GNOME Bugzilla – Bug 484281
crash in Panel:
Last modified: 2007-11-13 10:05:15 UTC
Version: 2.20.0.1 What were you doing when the application crashed? Distribution: Debian 4.0 Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22-grml #1 SMP PREEMPT Tue Jul 10 00:35:57 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 27336704 vsize: 27336704 resident: 14868480 share: 11386880 rss: 14868480 rss_rlim: 4294967295 CPU usage: start_time: 1191715014 rtime: 35 utime: 29 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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 -1225742672 (LWP 23424)] (no debugging symbols found) 0xb773ebce in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 168436
Thread 1 (Thread -1225742672 (LWP 23424))
----------- .xsession-errors --------------------- (gnome-panel:23424): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:23424): GLib-CRITICAL **: g_hash_table_remove: assertion `hash_table != NULL' failed /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: error: invalid identifier `tooltip_bg_color', expected valid identifier ** Message: failed to load session from /home/yazdzik/.nautilus/savedbnclZg /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:158: error: invalid identifier `tooltip_bg_color', expected valid identifier (nautilus:23425): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
Really looks like bug 446183 :/ Martin: did you see this only once or did it happen again? Also, if possible it'd be great to have better stack traces. Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 475065 ***