GNOME Bugzilla – Bug 513025
crash in Volume Control: Gnome gestartet
Last modified: 2008-01-30 10:54:55 UTC
What were you doing when the application crashed? Gnome gestartet Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23.12-slh-smp-2 #1 SMP PREEMPT Sun Dec 23 14:05:19 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 34324480 vsize: 34324480 resident: 11591680 share: 8646656 rss: 11591680 rss_rlim: 4294967295 CPU usage: start_time: 1201679363 rtime: 18 utime: 14 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e546b0 (LWP 4820)] (no debugging symbols found) 0xb7f21410 in __kernel_vsyscall ()
+ Trace 187331
Thread 1 (Thread 0xb6e546b0 (LWP 4820))
----------- .xsession-errors --------------------- --------------------------------- --------------------------------- It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/raz0rsedge/.DCOPserver_raz0rbox__0 and start dcopserver again. --------------------------------- (nautilus:4664): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch kbuildsycoca running... kdeinit: Communication error with launcher. Exiting! (gnome-panel:4663): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch Reusing existing ksycoca --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 512924 ***