On Fri, 28 May 2021, Simon McVittie wrote:
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,
Yes, you're right. It's still the older version of Nautilus. Yet it's not
just mount, libmount1 and other binary packages from util-linux but also
libselinux1, libsepol1 and libsemanage1 that I had to update because of
binary dependencies.
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.
I think it's hard to tell where the limitations are if several tools and
libraries interact together. It is certainly not Nautilus because it just
calls GMount::unmount_with_operation() from GIO (in
nautilus_file_operations_unmount_mount_full() for instance). I assume that
is the same for all of its descendants (Caja, Pantheon Files and alike).
So it makes sense to solve this further down in GIO/GVFS, FUSE or mount.
It is arguable where best and how exactly to fix this as you can see in
various discussions, e.g., https://gitlab.gnome.org/GNOME/gvfs/issues/133,
https://gitlab.gnome.org/GNOME/glib/issues/633,
https://github.com/libfuse/libfuse/issues/246 and
https://github.com/karelzak/util-linux/pull/705. In the end, it was done
in mount and libmount respectively. But this does not necessarily mean
that mount had a limitation.
Best regards,
Thomas Uhle
