GNOME Bugzilla – Bug 456310
crash in CD Player: Attempting to Play Audio...
Last modified: 2007-07-28 11:14:43 UTC
Version: 2.18.0 What were you doing when the application crashed? Attempting to Play Audio CD Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-Strawberry Icon Theme: Crux Memory status: size: 390774784 vsize: 390774784 resident: 17395712 share: 10620928 rss: 17395712 rss_rlim: 18446744073709551615 CPU usage: start_time: 1184260072 rtime: 25 utime: 20 stime: 5 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-cd' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496401904 (LWP 19561)] [New Thread 1115699536 (LWP 19589)] [New Thread 1094719824 (LWP 19585)] [New Thread 1084229968 (LWP 19580)] (no debugging symbols found) 0x0000003d15a0d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 147572
Thread 1 (Thread 46912496401904 (LWP 19561))
----------- .xsession-errors --------------------- ** (gnome-cd:19561): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:19561): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:19561): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:19561): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:19561): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:19561): WARNING **: ERROR: Could not open CD device for reading. warning: the debug information found in "/usr/lib/debug//usr/lib64/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so.debug" does not match "/usr/lib64/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so" (CRC m --------------------------------------------------
*** This bug has been marked as a duplicate of 336812 ***