Nautilus can't properly unmount FUSE file systems

Bug #254171 reported by Eivind Kjørstad
158
This bug affects 39 people
Affects Status Importance Assigned to Milestone
FUSE
Fix Released
Unknown
Files
Invalid
Undecided
Unassigned
Nautilus
New
Unknown
nautilus (Debian)
Fix Released
Unknown
nautilus (Ubuntu)
Fix Released
Wishlist
Unassigned
Nominated for Intrepid by Eivind Kjørstad
Nominated for Jaunty by Eivind Kjørstad

Bug Description

Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems.

However, if you right-click and select "unmount" you get a error-message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root.

This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname"

Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem.

Tested with encfs, likely to affect other similar filesystems like sshfs.

Affects both Hardy and Intrepid

Update: Tested with the latest jaunty-alpha, still present.

Tags: bionic xenial
description: updated
description: updated
Revision history for this message
Andrew (andrew-rw-robinson) wrote :

Confirmed as having this problem on Intrepid. Would seem to be simple to implement as the mount command sees the mount point and recognizes it as an fuse mounted folder.

Revision history for this message
Andrew (andrew-rw-robinson) wrote :

Work-around:

install nautilus-actions
Create a new action "Unmount fuse" with Path:
/bin/fusermount
And Parameters:
-u %M

Under conditions, select "Only folders"

Not as good as the unmount, but helpful if you want a UI approach

Revision history for this message
Sense Egbert Hofstede (sense) wrote :

Thank you for helping with making Ubuntu better by reporting this bug. This is actually a bug in Nautilus itself and not in Nautilus Actions, which is an extra that isn't even installed on most systems. I'm reporting this upstream.

summary: - Unmounting of fuser-filesystems fail
+ Nautilus can't properly unmount FUSE file systems
affects: nautilus-actions (Ubuntu) → nautilus (Ubuntu)
Changed in nautilus (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Changed in nautilus (Debian):
status: Unknown → New
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
importance: Unknown → Medium
Revision history for this message
Mike Doherty (doherty) wrote :

I've marked #417743 as a duplicate of this bug. It does have some helpful information, for example on reproducing this error.

Note that this bug still exists in Lucid.

Changed in nautilus:
status: New → Confirmed
Revision history for this message
Zisu Andrei (matzipan) wrote :

Hey. Is this bug going to be fixed anytime soon?

Right now, when I mount something with sshfs (fuse), it shows up in the "Devices" section of nautilus. But when I try to unmount it by pressing the eject button, I get this error: "mount: ... is not in the fstab (and you are not root)".

Revision history for this message
Leon (leonbo) wrote :

This one would be great for another "one hundred papercuts". Long standing, annoying little bug.

Revision history for this message
Danielle Foré (danrabbit) wrote :

Marking as "invalid" for Files since it's been marked upstream as being a bug in GVFS itself

Changed in pantheon-files:
status: New → Invalid
Norbert (nrbrtx)
tags: added: artful trusty xenial zesty
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in caja (Ubuntu):
status: New → Confirmed
Revision history for this message
Aravind R (araviaravi) wrote :

This happenns with me too. When mounnt smbd / unmount smmbd.

Revision history for this message
Andy Holmes (andyholmes) wrote :

There's an upstream bug for this[1], but no activity since 2012-08-21.

[1]: https://bugzilla.gnome.org/show_bug.cgi?id=607706

Changed in caja (Ubuntu):
status: Confirmed → Invalid
Norbert (nrbrtx)
no longer affects: caja (Ubuntu)
Norbert (nrbrtx)
tags: added: bionic
tags: removed: zesty
Norbert (nrbrtx)
tags: added: cosmic
removed: artful
Thomas Uhle (uhle)
Changed in nautilus:
importance: Medium → Unknown
status: Confirmed → Unknown
Changed in fuse (Debian):
status: Unknown → Fix Released
Revision history for this message
Thomas Uhle (uhle) wrote :

According to https://github.com/karelzak/util-linux/pull/705, this issue seems to have been fixed natively in mount/libmount1 from util-linux (since version 2.34). So it should work with Ubuntu 20.04 LTS (focal fossal) and newer.

Changed in nautilus (Ubuntu):
status: Triaged → Fix Released
Thomas Uhle (uhle)
affects: fuse (Debian) → fuse
Changed in nautilus:
status: Unknown → New
Changed in nautilus (Debian):
status: New → Fix Released
Norbert (nrbrtx)
tags: removed: cosmic trusty
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.