GNOME Bugzilla – Bug 513096
crash in Volume Control:
Last modified: 2008-01-30 18:16:17 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.8 #1 PREEMPT Fri Sep 28 20:40:22 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Zenith Icon Theme: nuoveXT.2.2 Memory status: size: 41062400 vsize: 41062400 resident: 15085568 share: 10199040 rss: 15085568 rss_rlim: 4294967295 CPU usage: start_time: 1201694900 rtime: 44 utime: 31 stime: 13 cutime:2 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6eda6b0 (LWP 3338)] 0xb7fa8410 in __kernel_vsyscall ()
+ Trace 187378
Thread 1 (Thread 0xb6eda6b0 (LWP 3338))
----------- .xsession-errors (48 sec old) --------------------- 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:2886): WARNING **: Host name lookup failure on localhost. Initializing nautilus-share extension Initializing nautilus-open-terminal extension ** Message: Orage **: Build alarm list: Processed 0 events. Found 0 alarms of which 0 are active. (Searched 0 recurring alarms.) seahorse nautilus module initialized Initializing gnome-mount extension Initializing nautilus-search-tool extension Initializing nautilus-image-converter 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 ***