Stuck KBFS on Debian after new private folder added
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm trying to access a private directory. I received notice over email, and in the GUI.
Clicking on the GUI gave an error, and the folder did not appear in /keybase/private
I tried restarting keybase using run_keybase (both as root and user - it appears that as-user is the correct form? perhaps docs could clarify this), and using systemctl.
Now, the GUI is running, but "ls /keybase" gives "permission denied", and "sudo ls /keybase" hangs forever.
Just submitted log with ID 1DKUelgv9g4Di8z2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Debian reproduction: add a private folder, attempt access in the GUI and /keybase/private, then compare run_keybase and systemctl behavior. Review the submitted log ID 1DKUelgv9g4Di8z2; done should mean the private folder is accessible and ls /keybase no longer fails or hangs, or the correct restart command is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100