GNOME Bugzilla – Bug 513205
crash in Volume Control:
Last modified: 2008-01-30 18:12:59 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23.20080114 #1 SMP PREEMPT Mon Jan 14 18:56:45 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gartoon Memory status: size: 47464448 vsize: 47464448 resident: 13844480 share: 10653696 rss: 13844480 rss_rlim: 4294967295 CPU usage: start_time: 1201716231 rtime: 14 utime: 10 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' (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 0xb6eb66b0 (LWP 20415)] (no debugging symbols found) 0xb7811321 in waitpid () from /lib/libpthread.so.0
+ Trace 187433
Thread 1 (Thread 0xb6eb66b0 (LWP 20415))
----------- .xsession-errors --------------------- (gnome-panel:20313): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 42 Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed (bluetooth-applet:20328): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:20313): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-settings-daemon:20303): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 (nautilus:20314): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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 513018 ***