Bug 238999 - Nautilus' umount volume also ejects it, when it should not
Summary: Nautilus' umount volume also ejects it, when it should not
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-04 12:19 UTC by Adriano Del Vigna
Modified: 2015-03-03 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 14:41:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adriano Del Vigna 2007-05-04 12:19:17 UTC
Description of problem:
When I try to umount a CD media volume, from Nautilus 'File->Unmount Volume'
menu item, it also ejects the media from CD drive. What makes impossible to use
an application like 'brasero', to erase a CD-RW, for example. I have to manually
open a terminal window, and as root umount the media volume to perform the
erasing through 'brasero'.


Version-Release number of selected component (if applicable):
nautilus-2.18.1-2.fc7

How reproducible:
Always.

Steps to Reproduce:
1.Insert a CD media into CD drive
2.Wait a few seconds for the system mount it and Nautilus open its window
3.Go to 'File->Unmount volume' menu item, it ejects the media
  
Actual results:
With the ejection of the media, further operations that requires the media to be
not mounted cannot be performed, like burning or erasing. At least with 'brasero'.

Expected results:
When I choose the described menu item, the media actually be umounted, and not
also ejected from the device. So other operations can be performed. I mean, that
the menu item accomplishes with what it stands for.

Additional info:
How to mount it after umount from Nautilus' menu item??

Comment 1 Bug Zapper 2008-05-14 02:51:29 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 lexual 2009-02-24 07:26:30 UTC
I can't reproudce this behaviour here with Fedora 10.
CD unmounts but doesn't eject.

Comment 3 Bug Zapper 2009-06-09 22:35:08 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-07-14 14:41:41 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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