Description of problem: Mountpoints that are under /mnt and are defined in /etc/fstab do not show up Version-Release number of selected component (if applicable): nautilus.x86_64 3.0.2-1.fc15 How reproducible: always Steps to Reproduce: 1. put a mountpoint in /etc/fstab like: storage:/media/Data1 /mnt/Data1 nfs defaults,noauto,users,bg 0 0 2. create the mountpoint, for the example: /mnt/Data1 3. 4. Actual results: mountpoint /mnt/Data1 does not show up in nautilus Expected results: mountpoint /mnt/Data1 should show up in nautilus. this used to work in f14 Additional info: see also #711140
That's correct. We don't show mounts from /mnt by purpose. Place them in /media instead, should be visible then. (In reply to comment #0) > Additional info: > see also #711140 Hah, nice conflict. Let me talk to those guys.
I think the best solution is to let nautilus/gvfs look at fstab and present user mountable mountpoints
(In reply to comment #2) > I think the best solution is to let nautilus/gvfs look at fstab and present > user mountable mountpoints Agreed. After all, what really makes the devices that Nautilus presents to the user so special? Is is the fact, that their mountpoints start with "/media"? No. It is the fact that they are {,un}mountable by the user.
any progress on this? it's rather annoying to go into the shell to mount a share
I'm having the same trouble on F16, but, my fstab mount entries are pointing to the /media directory. The difference with my problem, I believe, is that my fstab entry points to an apple time capsule that is only mountable as a cifs file system and not an nfs file system. The strange thing is that nautilus shows the devices and errors when trying to use those icons to mount the time capsule, though the mount succeeds. The error states that the mount operation has timed out. I'm able to browse to the location and see that the file system truly is mounted, but, the nautilus device buttons very rarely work as intended. Some times about 30 minutes to an hour later I receive the status notification that the mounted volume is ready at the bottom of the screen and other times it will never show.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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.
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.