Comment 20 for bug 203574

Same problem for me on two recent, fresh installs of Karmic, but here's the twist: This also affects KDE3.5.10 and XFCE 4.6, on two different machines with two completely different DVD devices (and a third that I threw out, thinking it was bad).

Could the same piece of software be responsible for this bug occurring on all three desktop environments?

Begin rant:

This bug was filed over a year and a half ago. Why is it still a problem!? Shortage of developers? Lack of time?

If I try to eject from the button on front, it often refuses, because the computer overrides me!

If I try to use the command line and it usually works - unless the computer overrides me!

If I try to eject using a paperclip in that little hole, it usually works - unless the computer overrides me!

(Do you folks see a pattern yet??)

I've used Linux for several years now, and I've watched some aspects of it really deteriorate over the last few years. Minor bugs I understand, but this kind of stuff defies the normal behavior of the computer (regardless of OS). Whatever caused this bug should have either been fixed or reverted long ago.

If I press the eject button, by $DIETY, that drive had better eject *unconditionally*. I don't care if there's a disc in the drive, I don't care if that disc is mounted or not, and I don't care if some random application throws an error! Eject the flippin' tray!

End rant.