GNOME Bugzilla – Bug 513369
crash in Volume Control: trying to add volume con...
Last modified: 2008-01-31 11:32:13 UTC
What were you doing when the application crashed? trying to add volume control to the panel Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22 #1 SMP Fri Oct 5 23:42:56 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 33136640 vsize: 33136640 resident: 12763136 share: 9646080 rss: 12763136 rss_rlim: 4294967295 CPU usage: start_time: 1201766999 rtime: 16 utime: 15 stime: 1 cutime:1 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6eb76b0 (LWP 7819)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187543
Thread 1 (Thread 0xb6eb76b0 (LWP 7819))
----------- .xsession-errors (357 sec old) --------------------- (gnome-panel:4646): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 26 kdeinit: Shutting down running client. --------------------------------- It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/mal/.DCOPserver_black__0 and start dcopserver again. --------------------------------- kbuildsycoca running... /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier capplet-common-Message: cleanup_cb: Enter --------------------------------------------------
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 ***