Can't get to Samba gvfs mount outside of Nautilus

Pretty much what the title says, I’m able to get to my Samba shares just fine within Nautilus, but not outside of it. Two main symptoms I’m seeing:

  1. No gvfs directory in /run/user/1000
  2. No “Open in Terminal” button in Nautilus

Here’s the output of gio info smb://dustin@localhost/dfs:

display name: dfs on localhost
edit name: /
name: /
type: directory
size:  0
uri: smb://dustin@localhost/dfs/
attributes:
  standard::type: 2
  standard::name: /
  standard::display-name: dfs on localhost
  standard::edit-name: /
  standard::icon: folder-remote, folder-remote-symbolic
  standard::content-type: inode/directory
  standard::fast-content-type: inode/directory
  standard::size: 0
  standard::allocated-size: 0
  standard::symbolic-icon: folder-remote-symbolic, folder-remote
  etag::value: 1727842042
  id::filesystem: smb-share:server=localhost,share=dfs,user=dustin
  access::can-trash: FALSE
  time::modified: 1727842042
  time::modified-usec: 607854
  time::access: 1727842318
  time::access-usec: 242000
  time::changed: 1727842042
  time::changed-usec: 607854
  unix::device: 1993426127
  unix::inode: 1

I’m using Fedora 40 with Gnome 46.

I have tried to systemctl --user restart gvfs-daemon as mentioned here on SE, but it didn’t seem to do any good. There isn’t anything overtly suspicious in the output of systemctl --user status gvfs-daemon:

● gvfs-daemon.service - Virtual filesystem service
     Loaded: loaded (/usr/lib/systemd/user/gvfs-daemon.service; static)
    Drop-In: /usr/lib/systemd/user/gvfs-.service.d
             └─00-uresourced.conf
             /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2024-10-01 23:02:09 CDT; 15min ago
   Main PID: 10224 (gvfsd)
      Tasks: 37 (limit: 19020)
     Memory: 39.1M (peak: 39.8M)
        CPU: 836ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/gvfs-daemon.service
             ├─10224 /usr/libexec/gvfsd
             ├─10317 /usr/libexec/gvfsd-recent --spawner :1.238 /org/gtk/gvfs/exec_spaw/1
             ├─10318 /usr/libexec/gvfsd-trash --spawner :1.238 /org/gtk/gvfs/exec_spaw/2
             ├─10491 /usr/libexec/gvfsd-smb --spawner :1.238 /org/gtk/gvfs/exec_spaw/4
             ├─11160 /usr/libexec/gvfsd-network --spawner :1.238 /org/gtk/gvfs/exec_spaw/5
             ├─11169 /usr/libexec/gvfsd-dnssd --spawner :1.238 /org/gtk/gvfs/exec_spaw/6
             ├─11175 /usr/libexec/gvfsd-wsdd --spawner :1.238 /org/gtk/gvfs/exec_spaw/7
             ├─11180 /usr/bin/python3 /usr/bin/wsdd --no-host --discovery --listen /run/user/1000/gvfsd/wsdd
             └─11705 /usr/libexec/gvfsd-smb --spawner :1.238 /org/gtk/gvfs/exec_spaw/12

Oct 01 23:02:09 dustin-pc systemd[1911]: Starting gvfs-daemon.service - Virtual filesystem service...
Oct 01 23:02:09 dustin-pc systemd[1911]: Started gvfs-daemon.service - Virtual filesystem service.
Oct 01 23:07:48 dustin-pc gvfsd[11180]: 2024-10-01 23:07:48,158:wsdd WARNING(pid 11180): no interface given, using all interfaces

What do you see after opening it in nautilus and using gio mount -l? Also, are you how are you running nautilus? Is it a default system package or a container/flatpak?

That is because the gvfsd-fuse daemon is not running. This is most probably because it isn’t installed. It is usually part of an extra package (e.g. gvfs-fuse in Fedora)…

1 Like

Thanks for the reply, got it figured out though! For posterity: I’m using the default system package.

This worked fine (to the best of my memory, at least) on Fedora 39 - any idea if it’s intentional that gvfs-fuse isn’t automatically installed anymore? I can always take to the Fedora forums at this point.

I doubt that it is something intentional. Are you sure it wasn’t installed by default? I see the gvfs-fuse package to be part of comps for the gnome-desktop group, which should be installed by default:
https://pagure.io/fedora-comps/blob/1a7a558db99d895dfb69468927d5d9c1dc7778ae/f/comps-f40.xml.in#_2633