Arch Linux

How does root get permission denied?

[root@viron ~]# ls -ld /run/user/1000/*
ls: cannot access /run/user/1000/gvfs: Permission denied
srw-rw-rw- 1 fp users 0 Oct 13 17:59 /run/user/1000/bus
drwx------ 2 fp users 60 Oct 13 23:12 /run/user/1000/dconf
drwx------ 2 fp users 60 Oct 13 17:59 /run/user/1000/gnome
drwx------ 3 fp users 60 Oct 13 17:59 /run/user/1000/gnome-shell
drwx------ 2 fp users 40 Oct 13 17:59 /run/user/1000/gvfs-burn
prw------- 1 fp users 0 Oct 13 17:59 /run/user/1000/kalu_fifo_1058
drwx------ 2 fp users 120 Oct 13 17:59 /run/user/1000/keyring
drwx------ 2 fp users 80 Oct 13 17:59 /run/user/1000/pulse
drwxr-xr-x 2 fp users 80 Oct 13 17:59 /run/user/1000/systemd

After marking /run/user/1000/gvfs owner-writable, my Google Drive mounted. Then after unmount/try to remount I found it read-only again.

The permission level of gvfs is read only for user:

$ ls -l
total 0
srw-rw-rw- 1 ogarcia ogarcia 0 oct 14 11:43 bus
drwx------ 2 ogarcia ogarcia 60 oct 15 09:27 dconf
drwx--x--x 2 ogarcia ogarcia 60 oct 14 11:43 gdm
drwx------ 2 ogarcia ogarcia 60 oct 14 11:43 gnome
drwx------ 3 ogarcia ogarcia 60 oct 14 11:43 gnome-shell
dr-x------ 2 ogarcia ogarcia 0 oct 14 11:43 gvfs
drwx------ 2 ogarcia ogarcia 40 oct 14 12:11 gvfs-burn
drwx------ 2 ogarcia ogarcia 120 oct 14 11:43 keyring
drwxr-xr-x 2 ogarcia ogarcia 60 oct 14 11:44 ownCloud
drwx------ 2 ogarcia ogarcia 80 oct 14 11:43 pulse
drwxr-xr-x 2 ogarcia ogarcia 80 oct 14 11:43 systemd

$ ls -ld gvfs
dr-x------ 2 ogarcia ogarcia 0 oct 14 11:43 gvfs

But you can read the contents without problems.

$ ls -la /run/user/1000/gvfs
total 0
dr-x------ 2 ogarcia ogarcia 0 oct 14 11:43 .
drwx------ 12 ogarcia ogarcia 260 oct 14 13:30 ..

Even so you can't mount any network shares.

Same problem but with sshfs here.

Connection to the server works fine, but nothing is actually being mounted to /run/user/1000/gvfs/


Until it's fixed I'll just have to mount stuff by hand.

not fixed with the last gvfs version (1.26.1.1-1).

I am now able to mount shares samba and NFS shares in Nautlus. I cannot mount Owncloud or Google Drive shares. Those throw a dialog box up that says "Volume doesn't implement mount."

are you able to get a VFS path with your mounted samba/nfs? In means you are able to list your remote shares through $XDG_RUNTIME_DIR/gvfs ?

Downgrading to gvfs version 1.26.0-3 as temporary workaround as I can confirm that the issue still exists (cannot view my NAS shares) in the latest version (1.26.1.1-1).

I have the same issue with SMB shares, cannot view in the /run/user/1000/gvfs but I can see them in thunar directly.

I'm using cinnamon but I think this may be related/relevant so I'm posting it here.

I have gvfs 1.26.1.1-1 installed and using Nemo I an unable to browse the network.

I am however able to go directly to the network share with 'smb://hostname/share' but when I'm trying to access the files in VLC or Audacious they complain that the folder doesn't exist and uppon further search is does seem that the share is not mounted in '/run/user/1000/gvfs'.

I have managed to narrow it down to if I 'killall gvfsd gvfsd-metadata gvfs-udisks2-volume-monitor' (notice i did not use sudo) and start them at the terminal by running '/usr/lib/gvfs/gvfsd', '/usr/lib/gvfs/gvfsd-metadata' and '/usr/lib/gvfs/gvfs-udisks2-volume-monitor' it will work correctly.

This is wierd because htop shows the above running with my user permissions so me killing them and starting them manually should not do anthing but is seems like they did not initialize correctly on startup.

Those that have this issue with gvfs >= 1.26.1, could you please compare the output or "tr '\000' '\n' </proc/PID/environ" for the PIDs of your systemd --user and your dbus-daemon?

tr '\000' '\n' < /proc/751/environ

LANG=en_GB.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
NOTIFY_SOCKET=/run/systemd/notify
HOME=/home/fuxy
LOGNAME=fuxy
USER=fuxy
SHELL=/bin/bash
MAIL=/var/spool/mail/fuxy
XDG_RUNTIME_DIR=/run/user/1000

sudo tr '\000' '\n' < /proc/808/environ

SHELL=/bin/bash
DBUS_STARTER_ADDRESS=unix:path=/run/user/1000/bus,guid=08842ecae0728f253f83abc65622d0c6
DISPLAY=:1
XDG_RUNTIME_DIR=/run/user/1000
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
MAIL=/var/spool/mail/fuxy
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,guid=08842ecae0728f253f83abc65622d0c6
USER=fuxy
XAUTHORITY=/run/user/1000/gdm/Xauthority
DBUS_STARTER_BUS_TYPE=session
LANG=en_GB.UTF-8
MANAGERPID=751
HOME=/home/fuxy
LOGNAME=fuxy

sudo tr '\000' '\n' < /proc/784/environ

DISPLAY=:1
HOME=/home/fuxy
LANG=en_GB.UTF-8
LOGNAME=fuxy
MAIL=/var/spool/mail/fuxy
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
SHELL=/bin/bash
USER=fuxy
XAUTHORITY=/run/user/1000/gdm/Xauthority
XDG_RUNTIME_DIR=/run/user/1000
MANAGERPID=751
LISTEN_PID=784
LISTEN_FDS=1
LISTEN_FDNAMES=dbus.socket

This is what I got for my user. Couldn't do it for the PID's of other users like gdm and dbus.

Er, which PID is which? And was this indeed done with gvfs 1.26.1? You should reboot after installing gvfs so that any remnants of gvfs 1.24 are gone.

Did as instructed reinstalled latest gvfs and rebooted. This is what I got.

systemd --user

LANG=en_GB.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
NOTIFY_SOCKET=/run/systemd/notify
HOME=/home/fuxy
LOGNAME=fuxy
USER=fuxy
SHELL=/bin/bash
MAIL=/var/spool/mail/fuxy
XDG_RUNTIME_DIR=/run/user/1000

dbus-daemon --config-file=/etc/at-spi2/accessability.conf --nofork --print-address 3

SHELL=/bin/bash
DBUS_STARTER_ADDRESS=unix:path=/run/user/1000/bus,guid=b9290b75836113c5947d211056232047
DISPLAY=:1
XDG_RUNTIME_DIR=/run/user/1000
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
MAIL=/var/spool/mail/fuxy
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,guid=b9290b75836113c5947d211056232047
USER=fuxy
XAUTHORITY=/run/user/1000/gdm/Xauthority
DBUS_STARTER_BUS_TYPE=session
LANG=en_GB.UTF-8
MANAGERPID=750
HOME=/home/fuxy
LOGNAME=fuxy

dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation

DISPLAY=:1
HOME=/home/fuxy
LANG=en_GB.UTF-8
LOGNAME=fuxy
MAIL=/var/spool/mail/fuxy
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
SHELL=/bin/bash
USER=fuxy
XAUTHORITY=/run/user/1000/gdm/Xauthority
XDG_RUNTIME_DIR=/run/user/1000
MANAGERPID=750
LISTEN_PID=783
LISTEN_FDS=1
LISTEN_FDNAMES=dbus.socket

Upstream bug: https://github.com/systemd/systemd/issues/1600

Please test with dbus 1.10.0-4 from [testing].

With dbus from testing sftp and smb mounts work as exacted.

I can confirm dbus 1.10.0-4 update fixes it.

I can also confirm that dbus1.10.0-4 update fixes the issue.

Even with the dbus update I still can't mount ssh/sftp from /etc/fstab (using sshfs as fs type), while mounting from "connect to server" kind of works: it connects to the host, but ignores the path passed after the server name.

Mounting from command line (mount /path/to/mountpoint) works as expected.

Relaunching the daemon seems to resolve the issue on MATE. Might also work on GNOME 3.18.

After upgrading to the dbus from testing, I can navigate to smb:// addresses and open files again; however, I still cannot browse (as in, see a list of) my local network shares with Thunar, which used to work.

For the record, the smbtree command DOES list the shares correctly.

I can confirm that with dbus 1.10.0-4 the issue is complety fixed.

Can navigate un smb:// ssh(sftp://) google-drive:// and davs:// without problem.

Yes, it's fixe. Thanks Jan. I think you can close.