fusermount: user has no write access to mountpoint /keybase

[iGormilhit]

Hi, On one of my devices (twiggy), I can't use the kbfs folders, but I don't encounter this problem on the other one (turkana).

On both devices, I'm running Archlinux and the keybase-bin from the AUR repositories. keybase version is:

Client:  1.0.17-20160920160056+1e8543e
Service: 1.0.17-20160920160056+1e8543e

In the keybase.kbfs.log I can read that it's a permission problem:

2016-09-21T08:22:39.137510 ▶ [INFO kbfs start.go:27] 002 KBFS version 1.0.2-20160920160056+7ab3317
2016-09-21T08:22:39.137556 ▶ [DEBU kbfs main.go:107] 003 Mounting: /keybase
2016-09-21T08:22:39.141594 ▶ [DEBU keybase login_state.go:889] 004 + LoginState: Running request loop
2016/09/21 08:22:39 mount helper error: fusermount: user has no write access to mountpoint /keybase
2016/09/21 08:22:39 mount helper error: fusermount: user has no write access to mountpoint /keybase
kbfsfuse error: (2) fusermount: exit status 1

First, I checked the permissions of the /keybase folder and set them to drwxr-xr-x 2 root root. I've also checked groups igor (who is my user), but saw no differences between the two devices.

my log id: ae0f5adba3e47177cca2c71c

[maxtaco]

Cc: linux specialists @oconnor663 and @cjb

[cjb]

Hi, sudo chown igor:root /keybase should fix it.

[oconnor663]

When keybase-bin is first installed, we mkdir /keybase && chmod 777 /keybase. Do you know if you manually changed the permissions on that folder after installation?

The downside of using chown instead of loose permissions is that kbfsfuse will break if you use it with a different user on the same machine. (Though we are currently limited to one user at a time.)

[iGormilhit]

@cjb Indeed, it fixed it. @oconnor663 No, I don't think I've manually change the permissions there after the installation.

The fact is, that on the other device, the permissions are drwxr-xr-x 2 root root and it's working fine. I tried also to remove the /keybase directory, and then to reinstall keybase, but without any change...

[johnnyRose]

FYI, I had a similar problem. But, when I changed the mount directory to be inside my home directory, everything worked fine. Changing the permissions of /keybase to match that of my home directory fixed the problem: sudo chmod -R 500 /keybase

[oconnor663]

Note for folks coming from Google: This thread is now obsolete. Recent versions of Keybase install a "root redirector" that allows multiple user accounts to use paths starting with /keybase at the same time. It's unlikely that anyone needs to change the ownership of that mountpoint anymore.