GNOME Bugzilla – Bug 513261
crash in Volume Control: nothing special - loggin...
Last modified: 2008-01-30 22:07:02 UTC
What were you doing when the application crashed? nothing special - logging into a gnome session Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23.14 #1 SMP PREEMPT Tue Jan 22 08:04:00 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Default Icon Theme: gnome Memory status: size: 40095744 vsize: 40095744 resident: 14364672 share: 10305536 rss: 14364672 rss_rlim: 4294967295 CPU usage: start_time: 1201725841 rtime: 24 utime: 18 stime: 6 cutime:0 cstime: 2 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 0xb6ea76b0 (LWP 15765)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187468
Thread 1 (Thread 0xb6ea76b0 (LWP 15765))
----------- .xsession-errors --------------------- * Searching for installed applications... ** (gnome-settings-daemon:15709): WARNING **: Module GnomeSettingsModuleScreensaver could not be started 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:15713): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:15713): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:15713): WARNING **: Can not get _NET_WORKAREA ** (nautilus:15713): WARNING **: Can not determine workarea, guessing at layout --------------------------------------------------
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 ***