keybase / keybase/client

fusermount: user has no write access to mountpoint /keybase

Open
#4,355 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with keybase.kbfs.log and the reported fusermount error, then compare the /keybase permissions and group membership on twiggy and turkana. Done means identifying why the affected device rejects the mount and confirming that KBFS mounts successfully for the user.

Written by the indexing model from the issue text.

Assessment

Tech stack
arch-linux, go, linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.