Red Hat Bugzilla – Bug 9499
CDROM mount extremely slow... no Audio CD capabilities...
Last modified: 2008-05-01 11:37:54 EDT
I am running a fresh installation of RedHat 6.1. Everything I have is working perfectly, except for the CDROM unit. Whenever I want to mount a data CD, I find that it takes a few minutes for it to mount. Then when I want to access the information on the CD, say for example that I want to read the contents of a particular README file on the CD, it takes a whole 30 seconds or more for the information within that file to be displayed. This is terribly annoying. The second problem is that I can't listen to Audio CDs. Whenever I pop in an audio CD, the CDROM unit will stop responding for another few minutes and then a small window pops up indicating the name of the particular audio CD. Nothing else. During this time, a warning pop up window appears indicating the following: gtcd ---sm -client-id 1184a2ee66000095073964200000010020019 I know it isn't a problem with my CDROM unit since it works perfectly under Windows98. I'm using GNOME and have installed all of the software errata available at RedHat's ftp servers. Does anyone have any ideas as to why this is happening? -Kyle
try turning off magicdev (rpm -e magicdev) and restart GNOME, see if your problems are solved. Some flakey hardware has troubles with this autorun mechanism.
I tried removing the magicdev as you said, but I get a message saying the following: error: removing these packages would break dependencies: magicdev is needed by gnome-core-1.0.54-2 Is there any way of uninstalling magicdev without affecting the gnome-core? -Kyle
Go to control center, open Peripherals -> CD Properties, and then turn off everything.
Did that a long time ago, and left all of the options off. Still no go. Any other suggestions? Do you have any particular questions I could answer to help you diagnose the problem? -Kyle
if you aren't running magicdev, then gtcd should not be trying to play audio cds automatically when you insert them. Make sure magicdev is truly off, and that gtcd is not running. You may have an extra copy of gtcd in memory that is fighting for control of the drive.