fstab causes duplicate entries for mounts which then are desynchonized as to mount state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
using the /media/
Simple (thought i) place this in fstab:
/media/
any user can mount it, it is no using /media/ mounts to minimize the possibility of 'automounters' conflict, what could go wrong?
Then i realized that the kernel (maybe?) creates another mountpoint from the squash file to /dev/loop0 when i or the root (on boot) mounts the file. I suppose they're supposed to be transparently coupled, umounting the 'real' dir removes the loopback and that is fine.
What's not fine is:
1. both show in Places in nautilus
2. on boot, if i don't specify 'noauto' (which i don't want), there is the very real possibility that nautilus gets confused and when i click on playstation it tells me that 'playstation_1.sqsh is already mounted by /dev/loop0', and only shows the option to 'mount' and not 'unmount' (even if it's already mounted as a simple cmd line tests) if i right click on the Playstation place item.
This is very similar to this bug:
https:/
but of course the current workaround of using UUIDs does not work since a squashfs mount is in fact, not a partition and therefore has no UUID and i need users anyway.
The bug upstream refereed in that report was closed 'fixed' but i think it was only partially fixed. Could you open a new bug report? I never could deal with opening bug reports on gnome, very user unfriendly place that bug report site is.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.
ProcVersionSign
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Sep 30 06:23:00 2016
GsettingsChanges:
b'org.
b'org.
b'org.
b'org.
b'org.
InstallationDate: Installed on 2016-09-25 (4 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)