Bug#942126: gvfs-fuse: /run/user/ID/gvfs/ empty after upgrade

[Cesare Leonardi]

Package: gvfs-fuse
Followup-For: Bug #942126

Hello Simon, sorry if my bug report was a bit scarce of information. I
was a bit in hurry when I wrote it. Now I try to remedy...


On Thu, 10 Oct 2019 19:44:44 +0100 Simon McVittie <smcv at debian.org> wrote:
> On Thu, 10 Oct 2019 at 19:24:48 +0200, Cesare Leonardi wrote:
> > Every time MATE desktop starts, it mounts several SMB share with a
> > command like that:
> > gio mount "smb://host/folder"
> 
> By what mechanism does it mount them?

This PC is integrated in an Active Directory domain and I login using a
domain user. Winbind (from Samba), pam_winbind and nsswitch are involved
in this.

In my MATE environment I mount some shares from:
System -> Preferences -> Personal -> Startup Applications
Here I have a startup program for each "gio mount".

Before upgrading gvfs to 1.42.1-1, each mounted share was accessible
from /run/user/ID/gvfs/. Real example:
====================
$ ls -o /run/user/11278/gvfs/
drwx------ 1 BERNI\leonardic    0 ago  8  2015 'smb-share:server=gam,share=ced'
drwx------ 1 BERNI\leonardic    0 giu  8  2017 'smb-share:server=gam,share=driver'
====================

Now the gvfs folder is not populated anymore.
In my initial report I forgot to add that the journal doesn't
apparentely show nothing useful to me.

But I've done some more tests and now I suspect that the culprit is fuse3.
Upgrading from 1.42.0+really1.38.1-1 to 1.42.1-1 I saw that gvfs-fuse
dependencies switched from libfuse2 to libfuse3-3 and the latter
suggests "fuse3". Do note that in this bug report I still use fuse2,
but these days I've tried to install "fuse3" (that replaces "fuse"
2.9.9): the result was terrible because then logging with my Active
Directory user failed, with big slowness on login and in other places.
In that situation the journal showed errors from pam_winbind but I don't
know how and why it's related to fuse. Since with fuse3 the system was
substantially unusable for me, I had to immediately revert to fuse 2.x.

Now I've also reverted gvfs to 1.42.0+really1.38.1-1, but let me know if
you want me to do some tests or if you need more information: I will
upgrade to the latest version for you then I'll revert afterward.

Thank you.

Cesare.



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gvfs-fuse depends on:
ii  fuse          2.9.9-2
ii  gvfs          1.42.0+really1.38.1-1
ii  libc6         2.29-2
ii  libfuse2      2.9.9-2
ii  libglib2.0-0  2.62.1-1

gvfs-fuse recommends no packages.

gvfs-fuse suggests no packages.

-- no debconf information