Bug#956009: gvfs: Nautilus not mounting filesystems in /run/user/1000/gvfs

Bill Wohler wohler at newt.com
Tue Apr 7 05:01:19 BST 2020


Simon McVittie <smcv at debian.org> wrote:

> On Sun, 05 Apr 2020 at 11:45:07 -0700, Bill Wohler wrote:
> > Since a recent upgrade to bullseye from stretch
> 
> 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).

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

> > 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.
> 
> 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.

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.

> > I didn't find a Debian glib package. The closest I found was
> > glib-networking:amd64, 2.64.1-1.
> 
> 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
> 

-- 
Bill Wohler <wohler at newt.com> aka <Bill.Wohler at nasa.gov>
http://www.newt.com/wohler/, GnuPG ID:610BD9AD



More information about the pkg-gnome-maintainers mailing list