Red Hat Bugzilla – Bug 190402
gnome-eject does not eject
Last modified: 2013-03-05 22:45:33 EST
Description of problem:
gnome-eject does not eject.
Here, eject means "open the drive tray".
The problem occurs with an empty drive.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Type "gnome-eject" from a terminal window.
The drive does not open.
The message "gnome-mount 0.4" is displayed.
The drive opens.
Without arguments, the device /dev/cdrom should open.
There is no documentation on what drive is opened by default,
but the "eject" command opens /dev/cdrom by default.
$ gnome-eject -d /dev/hdc
This does not open the drive either.
An error box is displayed that reads:
"Unable to mount media."
"There is probably no media in the drive."
If a disc is manually inserted in the drive and
the drive is manually closed,
then gnome-eject opens the drive.
The "eject" command opens the drive tray when the drive is empty.
I was expecting gnome-eject to behave the same way.
The "eject" command also has the useful option "-T" which will
open a closed drive and close an open drive.
$ ls -lF /dev/cd*
lrwxrwxrwx 1 root root 3 Apr 30 22:25 /dev/cdrom -> hdc
lrwxrwxrwx 1 root root 3 Apr 30 22:25 /dev/cdrom-hdc -> hdc
lrwxrwxrwx 1 root root 3 Apr 30 22:25 /dev/cdrom-hdd -> hdd
lrwxrwxrwx 1 root root 3 Apr 30 22:25 /dev/cdrw -> hdd
lrwxrwxrwx 1 root root 3 Apr 30 22:25 /dev/cdrw-hdd -> hdd
lrwxrwxrwx 1 root root 3 Apr 30 22:25 /dev/cdwriter -> hdd
lrwxrwxrwx 1 root root 3 Apr 30 22:25 /dev/cdwriter-hdd -> hdd
(In reply to comment #0)
> If a disc is manually inserted in the drive and
> the drive is manually closed,
> then gnome-eject opens the drive.
Should have said, "gnome-eject -d /dev/cdrom" opens the drive.
With a manually inserted disc,
"gnome-eject", without arguments, does not open the drive.
I expect the default drive to open.
Confirmed on F7.
This is basically two bugs, right? The first one is "gnome-eject doesn't have a
default drive" (which one could perhaps argue it shouldn't have) and the second
one is "gnome-eject doesn't work on an empty drive" (which I would consider a
real problem). The second one is covered here:
These bugs appear related.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.