As a Debian user, I experience exactly the same thing recently. Out of the blue, recently this started to happen, and I may have also noticed less frequency now that I am running 2.6.22-1, but this is hard to validate. When this problem happens, with my particular cd-rom, the external eject button, or using eject from the command line does not open the cd-rom door.
It turns out that somewhere along the line my 'hdparm' package updated, and I must have inadvertenly allowed it to overwrite my hdparm.conf. The result was that the cd-rom in question was no longer setup with dma and 32bit I/O. Fixing this seemed to solve my problem. For whatever reason, with DMA disabled, it appears some instability in the operation of the cd-rom can arise. hdparm -w /dev/hdh #(My LG GSA-4081B which was acting up is /dev/hdh) reset my IDE drive, putting me back to a responsive unit, where eject functions again. hdparm /dev/hdh #Outputs my settings, showing me that DMA is off, and I/O is only 16bit. Arghhh. hdparm -c1 -d1 /dev/hdh #Enabled the DMA and 32bit I/O The changes were made permanent by editing /etc/hdparm.conf to ensure these were set on boot (as they were once before the problem). My version of this issue was solved. I think some of the observations from Edgy vs. Fiesty, etc., may be more related to how the DMA / 32-bit I/O is setup on install and/or upgrade. cheers, iMac -- [Feisty] Launch cd-rom while there is no cd in the drive https://bugs.launchpad.net/bugs/107952 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
