After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772961 - Nautilus not recognizing partition is already mounted
Nautilus not recognizing partition is already mounted
Status: RESOLVED DUPLICATE of bug 772867
Product: gvfs
Classification: Core
Component: udisks2 volume monitor
1.30.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-10-15 00:34 UTC by leebickmtu
Modified: 2016-10-17 06:41 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screen recording of the issue (2.91 MB, video/webm)
2016-10-15 00:41 UTC, leebickmtu 		Details

Description leebickmtu 2016-10-15 00:34:39 UTC 
I have a storage drive with just 1 btrfs partition on it. My fstab is setup to mount the drive as such:

/dev/disk/by-uuid/9f2f5133-28b5-4980-a284-5eeda8fc58ad /mnt/9f2f5133-28b5-4980-a284-5eeda8fc58ad auto nosuid,nodev,nofail,x-gvfs-show 0 0

The partition is mounted correctly at startup to '/mnt/9f2f5133-28b5-4980-a284-5eeda8fc58ad'.

However Nautilus as of GNOME 3.22 does not seem to recognize that it is mounted. In 'Other Locations' the partition is listed by it's UUID with a red disk icon. And clicking it results in an error window. "Unable to access location - mount: only root can mount /dev/disk/by-uuid/9f2f5133-28b5-4980-a284-5eeda8fc58ad on /mnt/9f2f5133-28b5-4980-a284-5eeda8fc58ad"

As far as the "only root can mount" error, I have sudo rights on my user and the disk is already mounted. I can go to it's /mnt/<UUID> mount point and it is mounted.

Nothing has changed in the fstab and it worked fine under GNOME 3.20.
Comment 1 leebickmtu 2016-10-15 00:41:03 UTC 
Created attachment 337745 [details]
Screen recording of the issue
Comment 2 gedgon 2016-10-15 01:26:37 UTC 
It's propably an issue in gvfs introduced in https://git.gnome.org/browse/gvfs/commit/?id=b77369832fd6fb97e1f036998663f2488ff15022

Downgrade to 1.30.0 or revert mentioned commit. Probably relevant bugreport https://bugzilla.gnome.org/show_bug.cgi?id=772942
Comment 3 leebickmtu 2016-10-15 02:52:39 UTC 
I did not have a cached version of the gvfs 1.30.0 package for Arch so instead I reverted to gvfs 1.28.3.

This did fix the problem, confirming that gvfs 1.30.x contains the bug. Most likely the commit that gedgon mentioned.
Comment 4 leebickmtu 2016-10-15 03:02:42 UTC 
Found a copy of Arch's gvfs 1.30.0 packages now. So I further limited this bug to only existing in gvfs 1.30.1.
Comment 5 Ondrej Holy 2016-10-17 06:41:11 UTC 
Thanks for your bug report! I've already reverted the patches causing those issues and made an another release. I am sorry for the inconvenience...

*** This bug has been marked as a duplicate of bug 772867 ***