DVD drive unable to eject when empty and fails to recognise empty discs

[Mr.UNOwen]

In the past, this drive was working, but now (after a number of updates) its not working. I don't usualy use the drive, so I just recently noticed the problem. I need to burn a disc soon, so please fix this problem ASAP.

DVD drive: Samsung TS-H552B

Behaviors:
1. Can't eject when empty
           - does nothing but flash led when pressing the physical button
           - I have to physically force it open
           - doesn't happen when I have a disc inside
2. Get message "Unable to mount media." when I try to eject the drive by right clicking eject on the drive icon
3. It doesn't recognize empty discs.

[Chris Fletcher (fletch-brightsparks)]

On Mr.UNOwen's second point, I get this too when there is no disk in the drive.

It is a LiteOn DVD burner and I have also tried it with an old Compaq CDROM reader.

Also when I select Mount Volume (just above the Eject option on the menu) it does nothing when there is no disc in the drive, which is obvious really but it would be nice to have some notification that there is no media in the drive. (A bit more friendly for the average user).

(Note: I tried this in Hardy)

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.