Bug 193745 - volume label persists in nautilus sidebar after unmounting
volume label persists in nautilus sidebar after unmounting
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Depends On:
  Show dependency treegraph
Reported: 2006-06-01 02:39 EDT by Lucie Zahorikova
Modified: 2015-03-03 17:28 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 11:58:09 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 Lucie Zahorikova 2006-06-01 02:39:10 EDT
Description of problem:

When unmounting a volume, the volume label persists in nautilus sidebar.
Selecting the (umounted) volume from the menu causes error message and the
window disappears (but nautilus itself seems not to crash).

Version-Release number of selected component (if applicable):
nautilus 2.14.1-1.fc5.1

How reproducible:

every time

Steps to Reproduce:
1. insert CD and wait until it mounts
2. eject the CD
3. observe that the label of the CD is still present in nautilus sidebar
4. double-click on it
Actual results:
Nautilus throws a system error message, the window closes

Expected results:
Volume labels should vanish after the volume is umounted.
Nautilus throws "device not mounted" msg, the window stays the same.

Additional info:
I disabled the desktop icons using gconf and I umount devices using applet.
However I suppose the bug is not bound to the applet.
Comment 1 Lucie Zahorikova 2006-06-02 01:31:53 EDT
The message says: The folder contents could not be displayed. "MyLabel" couldn't
be found. Perhaps it has recently been deleted.

This is a silly bug and I believe easy to fix;)
Comment 2 Alexander Larsson 2006-09-04 12:46:23 EDT
Rawhide should not close the window in this case at least.
Comment 3 Bug Zapper 2008-04-03 23:00:54 EDT
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
the change.

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
Comment 4 Bug Zapper 2008-05-06 11:58:07 EDT
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.

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