GNOME Bugzilla – Bug 461155
crash in CD Player: Editing an emacs file.
Last modified: 2007-09-09 10:00:43 UTC
Version: 2.18.0 What were you doing when the application crashed? Editing an emacs file. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:18:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 341843968 vsize: 341843968 resident: 20873216 share: 16396288 rss: 20873216 rss_rlim: 18446744073709551615 CPU usage: start_time: 1185607642 rtime: 14 utime: 8 stime: 6 cutime:0 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496365040 (LWP 4502)] [New Thread 1084229968 (LWP 4519)] [New Thread 1105209680 (LWP 4517)] (no debugging symbols found) 0x0000003f66e0d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 151112
Thread 1 (Thread 46912496365040 (LWP 4502))
----------- .xsession-errors --------------------- ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. ** (gnome-cd:4502): WARNING **: ERROR: Could not open CD device for reading. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 336812 ***