Red Hat Bugzilla – Bug 971576
Network drive sidebar duplicate entry / eject icon issue
Last modified: 2015-01-09 19:05:07 EST
Description of problem:
I set up my ownCloud account in Fedora 19 beta and saw the WebDAV share in the left sidebar in Nautilus. I clicked it and it worked, but instead of merely adding an eject icon to that existing entry, it made a _second_ entry representing the connected drive with its own eject icon.
Shouldn't Nautilus merely use the same entry and add the eject icon to it when connected? Why two?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a bookmarked WebDAV entry in Nautilus (I think that's what the ownCloud Account config does?)
Two entries appear in the sidebar, one for the bookmark presumably (the one that's always there) and a new one for the connected share with an eject icon.
The existing entry (the bookmark?) should simply gain an eject icon.
This is https://bugzilla.gnome.org/show_bug.cgi?id=696279
This has been fixed in the current gvfs update.
It should not be closed until the update is pushed stable.
Update is in testing: https://admin.fedoraproject.org/updates/FEDORA-2013-10863/gvfs-1.16.3-1.fc19 . Please test and file feedback. Thanks.
I'm on Fedora 20 beta with gvfs 1.18.3 installed and I still see duplicated entries in Files (Nautilus) for my samba shares mounted with cifs, i.e. one under Network and another under Devices.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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.
Fixed in at least 21 (I think in final 20 too).