GNOME Bugzilla – Bug 395116
crash in Sound: clicked on sound from sy...
Last modified: 2007-01-18 12:07:54 UTC
Version: 2.16.0 What were you doing when the application crashed? clicked on sound from system drop down menu 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:32:54 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Max failures exceeded, exiting now ** (bug-buddy:5316): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 26046464 vsize: 0 resident: 26046464 share: 0 rss: 11423744 rss_rlim: 0 CPU usage: start_time: 1168456111 rtime: 0 utime: 19 stime: 0 cutime:17 cstime: 0 timeout: 2 it_real_value: 0 frequency: 1 Backtrace was generated from '/usr/bin/gnome-sound-properties' (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 -1208722608 (LWP 5313)] (no debugging symbols found) 0x00a94402 in __kernel_vsyscall ()
+ Trace 101046
Thread 1 (Thread -1208722608 (LWP 5313))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for the bug report. This bug has been fixed. The fix will be available in GNOME 2.16.3. Please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 363005 ***