GNOME Bugzilla – Bug 513403
crash in Volume Control: I was starting gnome
Last modified: 2008-01-31 11:33:07 UTC
What were you doing when the application crashed? I was starting gnome Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: NoiaWarm Memory status: size: 35540992 vsize: 35540992 resident: 14053376 share: 9781248 rss: 14053376 rss_rlim: 4294967295 CPU usage: start_time: 1201776202 rtime: 28 utime: 23 stime: 5 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 0xb6ee86b0 (LWP 3340)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187562
Thread 1 (Thread 0xb6ee86b0 (LWP 3340))
----------- .xsession-errors (8 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) 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 ** (x-session-manager:3229): WARNING **: Host name lookup failure on localhost. --------------------------------------------------
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 ***