GNOME Bugzilla – Bug 513630
crash in Volume Control:
Last modified: 2008-02-01 11:56:57 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: Nuvola Memory status: size: 33378304 vsize: 33378304 resident: 11186176 share: 8245248 rss: 11186176 rss_rlim: 4294967295 CPU usage: start_time: 1201851826 rtime: 44 utime: 34 stime: 10 cutime:4 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 0xb6ea16b0 (LWP 3594)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187709
Thread 1 (Thread 0xb6ea16b0 (LWP 3594))
----------- .xsession-errors (107 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) Initializing gnome-mount extension 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 --------------------------------------------------
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 ***