GNOME Bugzilla – Bug 474436
crash in CD Player: I recently upgraded from...
Last modified: 2007-09-09 09:56:55 UTC
Version: 2.16.1 What were you doing when the application crashed? I recently upgraded from FC5 to FC6 by installing fedora-release-6-4.noarch.rpm and running yum update. The CD player said my gstreamer config was wrong. I hit set-device, and picked a theme, and it crashed. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2239.fc5 #1 Fri Nov 10 13:04:06 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 89714688 vsize: 0 resident: 89714688 share: 0 rss: 35442688 rss_rlim: 0 CPU usage: start_time: 1189133544 rtime: 0 utime: 19 stime: 0 cutime:17 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-cd' (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 -1208625456 (LWP 3233)] 0x00377402 in __kernel_vsyscall ()
+ Trace 161036
Thread 1 (Thread -1208625456 (LWP 3233))
----------- .xsession-errors (470 sec old) --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** (gnome-panel:2916): WARNING **: No toplevel on which to load object 'clock_applet' ** (gnome-panel:2916): WARNING **: No toplevel on which to load object 'tray_applet' ** (gnome-panel:2916): WARNING **: No toplevel on which to load object 'pager_applet' ** (gnome-panel:2916): WARNING **: No toplevel on which to load object 'tasklist_applet' ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name --------------------------------------------------
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 380124 ***