GNOME Bugzilla – Bug 485230
crash in Volume Control:
Last modified: 2007-10-27 18:18:04 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-Lime Icon Theme: Fedora Memory status: size: 45744128 vsize: 45744128 resident: 19513344 share: 17080320 rss: 19513344 rss_rlim: 4294967295 CPU usage: start_time: 1191994242 rtime: 36 utime: 30 stime: 6 cutime:12 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/mixer_applet2' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209030320 (LWP 2376)] (no debugging symbols found) 0x002c2402 in __kernel_vsyscall ()
+ Trace 169146
Thread 1 (Thread -1209030320 (LWP 2376))
----------- .xsession-errors (20 sec old) --------------------- no fault of your own. If you can reproduce the crash, please notify the developers by reporting a bug at: http://developer.pidgin.im/simpleticket/ Please make sure to specify what you were doing at the time and post the backtrace from the core file. If you do not know how to get the backtrace, please read the instructions at http://developer.pidgin.im/wiki/GetABacktrace If you need further assistance, please IM either SeanEgn or LSchiere (via AIM). Contact information for Sean and Luke on other protocols is at http://developer.pidgin.im/wiki/DeveloperPages --------------------------------------------------
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 463147 ***