GNOME Bugzilla – Bug 390888
crash in Volume Control:
Last modified: 2007-01-04 17:56:22 UTC
What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:31:29 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- (bug-buddy:3297): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_close: assertion `priv->closed == FALSE' failed ** (bug-buddy:3297): WARNING **: Couldn't load icon for Movie Player ** (bug-buddy:3297): WARNING **: Couldn't load icon for Open Folder (bug-buddy:3328): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_close: assertion `priv->closed == FALSE' failed ** (bug-buddy:3328): WARNING **: Couldn't load icon for Desktop Background (bug-buddy:3328): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_close: assertion `priv->closed == FALSE' failed ** (bug-buddy:3328): WARNING **: Couldn't load icon for Movie Player ** (bug-buddy:3328): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 86401024 vsize: 0 resident: 86401024 share: 0 rss: 9805824 rss_rlim: 0 CPU usage: start_time: 1167457830 rtime: 0 utime: 12 stime: 0 cutime:10 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 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 -1209169696 (LWP 3326)] (no debugging symbols found) 0x009e1402 in __kernel_vsyscall ()
+ Trace 97949
Thread 1 (Thread -1209169696 (LWP 3326))
This is probably related to the other bug as well, so I'm marking as duplicate, too. Feel free to reopen if this is not the case. *** This bug has been marked as a duplicate of 389421 ***
I had simply booted up the system ... no other button was clicked or anything. Also, it looks like this is causing the system itself not to start up properly meaning - first this crashes, then the bug reporting window shows up which seems to be going in an infinite loop (as can be guessed from the multiple messages that I ended up logging !) and then I do not have any option but to press the 'reset' button for the system to reboot as nothing else works !!! I have removed the 'volume control' from the panel for now and will observe for some more time. Cheers, Rahul.