GNOME Bugzilla – Bug 513728
crash in Volume Control: login
Last modified: 2008-02-01 18:15:11 UTC
What were you doing when the application crashed? login Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 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: 34459648 vsize: 34459648 resident: 13729792 share: 9637888 rss: 13729792 rss_rlim: 4294967295 CPU usage: start_time: 1201886889 rtime: 29 utime: 24 stime: 5 cutime:2 cstime: 4 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 0xb6e446b0 (LWP 18778)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187752
Thread 1 (Thread 0xb6e446b0 (LWP 18778))
----------- .xsession-errors (25 sec old) --------------------- SESSION_MANAGER=local/sniper:/tmp/.ICE-unix/18528 /dev/dsp: Device or resource busy ** (gnome-settings-daemon:18597): WARNING **: Could not start GNOME sound. 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 ** (gnome-session:18528): WARNING **: Failed to start sound. Window manager warning: Failed to read saved session file /home/sniper/.metacity/sessions/default0.ms: Failed to open file '/home/sniper/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized Initializing gnome-mount extension --------------------------------------------------
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 ***