GNOME Bugzilla – Bug 513271
crash in Volume Control: Adding the volume contro...
Last modified: 2008-01-30 22:07:30 UTC
What were you doing when the application crashed? Adding the volume control applet, it crash when the X session starts 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: 34242560 vsize: 34242560 resident: 13488128 share: 10219520 rss: 13488128 rss_rlim: 4294967295 CPU usage: start_time: 1201727421 rtime: 22 utime: 18 stime: 4 cutime:1 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 0xb6e746b0 (LWP 12627)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187474
Thread 1 (Thread 0xb6e746b0 (LWP 12627))
----------- .xsession-errors (239 sec old) --------------------- END checking gmail account migatxu ... BEGIN checking gmail account migatxu ... END checking gmail account migatxu ... BEGIN checking gmail account migatxu ... END checking gmail account migatxu ... BEGIN checking gmail account migatxu ... END checking gmail account migatxu ... BEGIN checking gmail account migatxu ... END checking gmail account migatxu ... BEGIN checking gmail account migatxu ... END checking gmail account migatxu ... BEGIN checking gmail account migatxu ... END checking gmail account migatxu ... BEGIN checking gWarning: more than one line! sh: jackd: command not found --------------------------------------------------
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 ***