GNOME Bugzilla – Bug 512060
crash in Panel:
Last modified: 2008-01-25 18:07:50 UTC
Version: 2.20.1 What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.20.1 2008-01-15 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.22-gentoo-r2 #2 Sat Dec 15 14:30:00 BRST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 151728128 vsize: 151728128 resident: 19529728 share: 14450688 rss: 19529728 rss_rlim: 18446744073709551615 CPU usage: start_time: 1201260986 rtime: 31 utime: 28 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47027276140736 (LWP 5460)] 0x00002ac5620ffad5 in waitpid () from /lib/libpthread.so.0
+ Trace 186772
Thread 1 (Thread 47027276140736 (LWP 5460))
----------- .xsession-errors (6 sec old) --------------------- Bonobo-Activation-Message: registration of 'OAFIID:GNOME_PanelShell' returns (success) Bonobo-Activation-Message: Successfully registered `OAFIID:GNOME_PanelShell' /usr/share/themes/Crux/gtk-2.0/gtkrc:137: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Crux/gtk-2.0/gtkrc:137: error: invalid identifier `tooltip_bg_color', expected valid identifier (gnome-panel:5460): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Initializing gnome-mount extension (gnome-panel:5460): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 25 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 453033 ***