Since a recent upgrade to bullseye from stretch, navigating to a remote
Samba directory via Nautilus or running "gio mount smb://server/share"
no longer creates a mount point in /run/user/1000/gvfs.

I found [1] which may be helpful. There's a glib packaging fix suggested
at the end. I tried the suggested workaround [2] to no avail. I didn't
find a Debian glib package. The closest I found was
glib-networking:amd64, 2.64.1-1.

1. https://github.com/NixOS/nixpkgs/issues/50254
2. systemctl --user stop gvfs-daemon

I marked this important since my scripts that depend on this directory
are broken until the directory is populated, or I read some
documentation that points out that the mounts can be found elsewhere. So
far, all of the documentation points to /run/user/1000/gvfs or
$XDG_RUNTIME_DIR/gvfs, which is empty.

In case it is useful, here are some diagnostics after running [2]
and mounting a remote filesystem in nautilus.

    [wohler@olgas doc]$ systemctl --user stop gvfs-daemon
    [Mount somedirectory from somehostname in Nautilus.]
    [/var/log/syslog]
    Apr  5 10:50:59 olgas systemd[3267]: Stopping Virtual filesystem service...
    Apr  5 10:50:59 olgas systemd[3267]: gvfs-daemon.service: Succeeded.
    Apr  5 10:50:59 olgas systemd[3267]: Stopped Virtual filesystem service.
    Apr  5 10:51:20 olgas dbus-daemon[7865]: [session uid=1000 pid=7865] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.140' (uid=1000 pid=14616 comm="gio mount --list ")
    Apr  5 10:51:20 olgas systemd[3267]: Starting Virtual filesystem service...
    Apr  5 10:51:20 olgas dbus-daemon[7865]: [session uid=1000 pid=7865] Successfully activated service 'org.gtk.vfs.Daemon'
    Apr  5 10:51:20 olgas systemd[3267]: Started Virtual filesystem service.

    [Starting Nautilus]
    Apr  5 10:54:05 olgas dbus-daemon[7865]: [session uid=1000 pid=7865] Activating service name='org.gnome.Nautilus' requested by ':1.39' (uid=1000 pid=8340 comm="/usr/bin/gnome-shell ")
    Apr  5 10:54:05 olgas dbus-daemon[7865]: [session uid=1000 pid=7865] Successfully activated service 'org.gnome.Nautilus'
    Apr  5 10:54:05 olgas org.gnome.Nautilus[14669]: Initializing nautilus-dropbox 2019.02.14
    Apr  5 10:54:05 olgas dbus-daemon[679]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1969' (uid=1000 pid=14669 comm="/usr/bin/nautilus --gapplication-service ")
    Apr  5 10:54:05 olgas systemd[1]: Starting Hostname Service...
    Apr  5 10:54:05 olgas dbus-daemon[679]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Apr  5 10:54:05 olgas systemd[1]: Started Hostname Service.

    [Navigating to Samba filesystem.]
    [No output in /var/log/syslog.]

    [wohler@olgas ~]$ gio mount --list
    ...
    Mount(1): public on <hostname> -> smb://somehostname/somedirectory>/
      Type: GDaemonMount

    [wohler@olgas ~]$ ls /run/user/1000/gvfs
    [wohler@olgas ~]$

Skipping a version when upgrading is not supported. Each version of Debian
represents about 2 years of development, and an upgrade path that applies
4 years of changes in a single transaction (and in particular ends up
running user-space processes on a kernel 4 years older than the one they
were tested with) is not something we can rely on.

If you have other Debian 9 'stretch' systems, please upgrade them to
Debian 10 'buster' and reboot, before attempting to upgrade to bullseye
(which is going to be Debian 11 when it gets released).

Do you have gvfs-fuse installed? That's the package that is responsible for
mounting these FUSE filesystems in Debian. Perhaps it should be a
Recommends or Suggests; we should certainly set up the reportbug metadata
so that when you report gvfs bugs, the presence or absence of gvfs-fuse is
part of the bug report.

The source package for GLib in Debian is glib2.0, and the actual shared
library is in the libglib2.0-0 binary package. You have version 2.64.1-1,
according to reportbug.

    smcv

Simon McVittie <smcv@debian.org> wrote:

Yes, I'm aware that you can only ungrade one release at a time, so
that's what I did.

It was not. Installing it installed fuse3 that produced an unmet
dependency that was resolved by removing fuse 2.9.9.

After a reboot, mounting the filesystem in both Nautilus and with gio
mount produced the mount point in /run/user/1000/gvfs. Thank you.

Note that I tend not to install Recommends or Suggests packages unless
it is obvious that I need it. The name "gvfs-fuse" may not have been
enough for me to know that this package would provide this utility.
Isn't this basic enough functionality that it should be required?

Anyway, many thanks for providing the solution! Anything you and other
Debian developers can do to help others avoid this situation is very
much appreciated.

This bug seems to have resurfaced with the current build of gvfs on
debian sid (1.57.2-1+b1).

After updating, my backups using borg over sftp started failing saying
that the repository couldn't be found. The repo was mounted and
accessible, but /run/user/1000/gvfs was empty.

Reverting the gvfs packages to 1.57.2-1 has fixed the issue.

Please report a new bug for an issue that only recently appeared even
if the bug seems similar to an old one. You can mention the related
bug in your new bug report.

Also, please try to keep the bug title in your subject line when
replying to bugs since the bug emails do not automatically include the
bug title.

Thank you,
Jeremy Bícha