GNOME Bugzilla – Bug 375373
crash in Volume Control: I had just rebooted and ...
Last modified: 2007-07-26 04:44:47 UTC
What were you doing when the application crashed? I had just rebooted and was logging in and I received the error while gnome was still loading. I just yesterday upgraded from Dapper to Edgy and have been experiencing problems since the upgrade. I had just rebooted because I was unable to login (my session would crash within 10 seconds and I would get the warning that my session had lasted less than 10 seconds and this may be because of an installation problem). This time instead of my session ending within 10 seconds, I got this bug reporting tool. If you can tell me what I need to do to get my Ubuntu back to normal, I would really appreciate it! Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 57208832 vsize: 0 resident: 57208832 share: 0 rss: 3698688 rss_rlim: 0 CPU usage: start_time: 1163555152 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/mixer_applet2' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226565968 (LWP 5720)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 86550
Thread 1 (Thread -1226565968 (LWP 5720))
*** Bug 375374 has been marked as a duplicate of this bug. ***
*** Bug 375376 has been marked as a duplicate of this bug. ***
*** Bug 375378 has been marked as a duplicate of this bug. ***
*** Bug 375388 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 354483 ***
*** Bug 447600 has been marked as a duplicate of this bug. ***