GUI and KBFS bugs in 5.9.0 on Windows and Linux
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Since upgrading to 5.9.0 on Windows 11, keybase does not fully start. The GUI is stuck on a Loading message and kbfs is not mapped to K: or any other drive letter. This would seem to be the same issue as reported in https://github.com/keybase/client/issues/24745 and https://github.com/keybase/keybase-issues/issues/4087.
I have also experienced a similar issue using the linux client (for debian-based systems). Upon upgrading to 5.9.0, kbfs would not cleanly mount at /keybase, though the GUI did seem to work as expected, and I found my keybase files could be accessed at /run/user/<uid>/keybase/kbfs.
On linux I was able to downgrade to 5.8.1 and set an apt hold to prevent re-upgrading to 5.9.0.
my log id: 23ad4baebe37f3d92088101c
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
The issue names no files, tests, or entry points. Start by reproducing the 5.9.0 upgrade behavior on Windows 11 and a Debian-based Linux system, then use log id 23ad4baebe37f3d92088101c and compare with issues 24745 and 4087. Done means the GUI starts normally and KBFS mounts at the expected Windows drive letter and /keybase path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100