Bug 161122 - Typo when mounted drive deleted
Typo when mounted drive deleted
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: nautilus (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2005-06-20 13:37 EDT by Kevin Fischer
Modified: 2015-01-07 19:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:59:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kevin Fischer 2005-06-20 13:37:03 EDT
Description of problem:
When a mounted drive is moved to the trash (or deleted) a dialog box comes up
indicating that the user should right click on the drive and click "eject". The
true menu option, however, is "unmount volume".

Version-Release number of selected component (if applicable):

How reproducible:
Mount a drive and try to delete it.

Steps to Reproduce:
1. Mount drive
2. Try to delete drive
3. Follow instructions in dialog
Actual results:
This isn't really applicable here.

Expected results:

Additional info:
Comment 1 Kevin Fischer 2005-06-21 15:16:19 EDT
Note: the message is valid for a CD drive, and most likely other types of drives
that actually list "eject". The error was encountered when a mounted network
drive was trashed.
Comment 2 RHEL Product and Program Management 2007-10-19 14:59:46 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.