Version: unspecified (using KDE 4.7.4) OS: Linux After copying a large file off a DVD (1GB+), the hardware eject button is ignored, you have to unmount using KDE's eject button and then push the hardware eject button. Reproducible: Always Actual Results: Expected Results:
*** This bug has been marked as a duplicate of bug 296965 ***
I don't see that bug as a duplicate. It never said anything about the hardware eject button.
Does this still happen with KDE 4.8?
No
This's reproducable with 4.8.3 again, and this time the behaviour is yet more strange. If I press the hardware eject button once, even the software eject button will stop working... it does nothing at all. And then if I eject it using cdrecord/wodim, KIO (?) will refuse to realize that the drive has been ejected; the disk will be avilable (in the places panel and device notifier) even after I've removed the disk. And cause all of the data has been cached, I can even copy it without the actual; disk being avilable. Placing a new disk makes no difference; KIO is forzen for that disk.
KDE 4.9 -- hardware eject button has no action, after I press it, KIO does not hang for the device and I can still eject it. Also notice that if I do not open the mounted disk in Dolphin, the hardware eject button works fine but false notification of the disk's presence remains in the device notification applet.
KDE 4.9.1 -- ejection mechanism behaves yet more weirdly, once the tray starts to eject, it gets inside again. I've to play games with it to remove a disk.
This is fixed in 4.9.2, reopen if the problem persists
No, hardware eject button doesn't work yet.
Update 4.9.4 -- software eject button has stopped working completely. It complains device is busy, and if I press the hardware eject button, it does eject but there's a zombie entry in the device notifier which says the disk is still mounted. I've to restart the external drive to fix the issue. umouting manually and then pressing the hardware eject button doesn't cause zombie entries to appear.
*** This bug has been marked as a duplicate of bug 311613 ***