GNOME Bugzilla – Bug 513293
crash in Volume Control: Re-logging into GUI afte...
Last modified: 2008-01-31 11:29:59 UTC
What were you doing when the application crashed? Re-logging into GUI after using update-manager. 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: 42565632 vsize: 42565632 resident: 13328384 share: 9613312 rss: 13328384 rss_rlim: 4294967295 CPU usage: start_time: 1201731310 rtime: 52 utime: 45 stime: 7 cutime:73 cstime: 19 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 0xb6eb26b0 (LWP 1951)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187487
Thread 1 (Thread 0xb6eb26b0 (LWP 1951))
----------- .xsession-errors --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) 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 ** (update-notifier:1910): WARNING **: hal_initialize failed: (null) --------------------------------------------------
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 ***