Bug#514453: , #757535: [caja|nautilus]: should properly unmount fuse mounts

[Simon McVittie]

Control: reassign 514453 mount 2.33.1-0.1
Control: affects 514453 = nautilus
Control: reassign 757535 mount 2.33.1-0.1
Control: affects 757535 = caja

On Thu, 27 May 2021 at 17:51:24 +0000, Mike Gabriel wrote:
> On  Do 27 Mai 2021 17:05:40 CEST, Thomas Uhle wrote:
> > according to https://github.com/karelzak/util-linux/pull/705, this old
> > issue seems to finally have been fixed natively in mount/libmount1 from
> > util-linux (since version 2.34). That was too late for Debian 10
> > (buster), but it should work with the upcoming Debian 11 (bullseye).
> 
> I sense we should close this bugs then and mark it as fixed in
> util-linux/2.34-1.

For now I'm reassigning these bugs from the file managers nautilus
(#514453) and caja (#757535) to mount, with "affects" on the file
managers.

I confirm that mounting a filesystem with "sshfs host:/dir ~/mnt" and
unmounting it through Nautilus works on current unstable, and the PR that
Thomas referenced seems like a plausible candidate for the upstream fix.
So I think we can close this as fixed in mount/2.36.1-7 or even
mount/2.34-1 (it isn't particularly important which one) after the reassign
gets processed.

On Fri, 28 May 2021 at 15:00:04 +0200, Thomas Uhle wrote:
> As far as I can confirm, it is working with sshfs/3.7.1+repack-1 together
> with mount/2.36.1-7 and libmount1/2.36.1-7 resp. which are the currently
> packaged versions for bullseye. I have never tested an older version of
> mount from util-linux after version 2.33.1-0.1 because I am basically still
> on Debian 10 (buster)

To confirm, does this mean you are still using buster's version of either
caja or nautilus, and the mount upgrade resolved this for you? If yes,
that seems like good evidence that this was a limitation of older versions
of mount (util-linux), rather than a limitation of older versions of
caja and nautilus.

    smcv