GNOME Bugzilla – Bug 513809
crash in Volume Control: Just after login, have n...
Last modified: 2008-02-02 10:28:28 UTC
What were you doing when the application crashed? Just after login, have not got a chance to do anything yet. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 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: 33067008 vsize: 33067008 resident: 13516800 share: 9527296 rss: 13516800 rss_rlim: 4294967295 CPU usage: start_time: 1201909956 rtime: 88 utime: 65 stime: 23 cutime:0 cstime: 5 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 0xb6f096b0 (LWP 3297)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187799
Thread 1 (Thread 0xb6f096b0 (LWP 3297))
----------- .xsession-errors (36 sec old) --------------------- Warning: No symbols defined for <I77> (keycode 247) Warning: No symbols defined for <I78> (keycode 248) Warning: No symbols defined for <I79> (keycode 249) Warning: No symbols defined for <I7A> (keycode 250) Warning: No symbols defined for <I7B> (keycode 251) Warning: No symbols defined for <I7C> (keycode 252) Warning: No symbols defined for <I7D> (keycode 253) Warning: No symbols defined for <I7E> (keycode 254) Warning: No symbols defined for <I7F> (keycode 255) seahorse nautilus module initialized 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 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 ***