GNOME Bugzilla – Bug 506687
crash in CD Player:
Last modified: 2008-01-19 16:38:53 UTC
Version: 2.18.0 What were you doing when the application crashed? 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 94322688 vsize: 94322688 resident: 18546688 share: 11350016 rss: 18546688 rss_rlim: 4294967295 CPU usage: start_time: 1199195423 rtime: 196 utime: 182 stime: 14 cutime:2 cstime: 0 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208400160 (LWP 7538)] [New Thread -1210528880 (LWP 7637)] [New Thread -1221227632 (LWP 7635)] [New Thread -1232290928 (LWP 7634)] (no debugging symbols found) 0x001e5402 in __kernel_vsyscall ()
+ Trace 183701
Thread 1 (Thread -1208400160 (LWP 7538))
----------- .xsession-errors (6 sec old) --------------------- ** (gnome-cd:7538): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:7538): WARNING **: ERROR: Could not open CD device for reading. (gnome-cd:7538): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed ** (gnome-cd:7538): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:7538): WARNING **: ERROR: Could not open CD device for reading. (gnome-cd:7538): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed ** (gnome-cd:7538): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:7538): WARNING **: ERROR: Could not open CD device for reading. --------------------------------------------------
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 458788 ***
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 485788 ***