Samba mounts no longer accessible at /run/user/1000/gvfs/smb-share/

Applications
,
1

I have several samba bookmarks/mounts in Nautilus, and file operations within Nautilus work fine.
However I used to be able to e.g. open a terminal in the smb folder (right-click open in terminal) or open media files in VLC by doubleclick, and that stopped working since several days/weeks.

I am on Debian Testing (trixie/6.12.19-amd64), gnome 48.0

VLC tells me that it can not open the location:
file:///run/user/1000/gvfs/smb-share%3Aserver%3Dnas.local%2Cshare%3Dmedia/test.mp4

Anyone has the same problem and knows why that is happening and how to fix it?

Regards

2

Try copying /usr/share/applications/vlc.desktop to ~/.local/share/applications, open it in a text editor and change the %U in the Exec line to a %F.

3

Thanks, however did not change anything.
copied, edited, and rebooted, still vlc has the same error with the same url.

4

I just realized that wasn’t a smb:// URL in the error message, and had thought of the wrong problem.

Does /run/user/1000/gvfs/ exist and contain the smb mount? If not, is gvfsd-fuse running?

5

Both ls /run/user/1000/gvfs/ as well as ps ax | grep gvfsd-fuse returns no result.

6

Is the gvfs-fuse package installed?

7 
# apt search gvfs-fuse
gvfs-fuse/testing,now 1.57.2-1+b1 amd64  [Installed,automatic]
8

same behavior for me, same config (debian testing, gnome 48)
VLC & smplayer fails to open files located on SMB share.
opening the file with “video” app (totem) works.

9

ah, right, same for the image apps, “gnome loupe” works, other image apps (e.g. Shotwell, XnView, …) don’t.

10

Does starting /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -d show any errors? (or wherever Debian puts the executable, the website where I usually look this up is not loading)

11

Not sure if relevant, i checked my apt history for gvfs/fuse related entries:

2 days ago (2025-03-26) apt upgrade did the following (and more):

  • INSTALL libfuse3-4:amd64 (3.17.1~rc1-3, automatic)
  • UPGRADE gvfs-fuse:amd64 (1.57.2-1, 1.57.2-1+b1)
  • UPGRADE gvfs:amd64 (1.57.2-1, 1.57.2-1+b1)
    (same for other gvfs packages)
  • UPGRADE fuse3:amd64 (3.14.0-10, 3.17.1~rc1-3)
12

running it as primary user (not root), right?

# find /usr -iname "gvfsd-fuse"
/usr/lib/gvfs/gvfsd-fuse
/usr/libexec/gvfsd-fuse
# echo $UID
1000
# /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -d
FUSE library version: 3.17.1-rc1
nullpath_ok: 0
unique: 2, opcode: INIT (26), nodeid: 0, insize: 104, pid: 0
INIT: 7.41
flags=0x73fffffb
max_readahead=0x00020000
fuse: both 'want' and 'want_ext' are set
   unique: 2, error: -71 (Protokollfehler), outsize: 16
13 

FUSE library version: 3.17.1-rc1
nullpath_ok: 0
unique: 2, opcode: INIT (26), nodeid: 0, insize: 104, pid: 0
INIT: 7.41
flags=0x73fffffb
max_readahead=0x00020000
fuse: both 'want' and 'want_ext' are set
   unique: 2, error: -71 (Erreur de protocole), outsize: 16
14

So this seems to be: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101305

1 Like
15

Yesterdays upgrade to gvfs 1.57.2-2 seems to have it fixed for me.

1 Like