Bugzilla – Bug 668198
11.4 M6 KDE Live CD ejects wrong device
Last modified: 2011-02-16 09:26:10 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 The built-in CD drive on my computer gets errors when reading media created on another device, thus I use an external USB drive for installation; however, the built-in drive is still in the configuration. When installation is finished, and the first reboot is started, the CD eject command is sent to the built-in driver, not the drive being used. On a running live system, the df command shows that the CD is mounted on /dev/sr1. Both /dev/cdrom and /dev/cdrw link to /dev/sr0, while /dev/cdrom1 and /dev/cdrw1 link to /dev/sr1. It appears that the script is ejecting the CD on /dev/cdrom without testing if that is really the drive on which the medium is mounted. This situation would likely occur on any 2 optical drive system that has been booted from the second drive. Reproducible: Always Steps to Reproduce: 1. 2. 3.
The eject as it is now, is completely useless, because the typical cases are: a) you have 1 CD-drive - eject will fail because it is in use (said coolo). There is also the text "if the Live CD is not ejected" suggesting, that eject might work. b) you have 2 CD-drives or install from USB - there it will eject an unused CD-drive.
This isn't a kernel issue. The kernel isn't ejecting the wrong device. The installer is telling the kernel to eject the wrong device.
the installer shouldn't try to eject at all - it's impossible it can eject its own file system.
To stop ejecting the CD from some reason works. Anyway, YaST can stop it rather easily, I will just need to update relevant pop-up (shorten it). Coolo, can that still be handled regarding translations?
perhaps some drives don't care if they are locked? But breaking translations now is not a good idea - especially in such a prominent place and when it wasn't a big problem for years.
OK, will fix this after 11.4 is out.
Reported already *** This bug has been marked as a duplicate of bug 511210 ***