Win10 client hangs on "loading..." even after reinstall
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Launching Keybase brings up the GUI window but it never moves past "loading...". Sometimes status tray window displays "logged-in" interface, other times it doesn't; KBFS is inaccessible and unusuable. Error reported is that keybased.sock doesn't exist (and it doesn't); system PATH and environment variables don't seem to be different from a working Win10 installation in a way that would break Keybase. Log report ID: 10e8828c05267710cdc5191c
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 log report 10e8828c05267710cdc5191c and the Windows client startup and service logs, focusing on why keybased.sock is not created after launch or reinstall. Compare the failing behavior with a working Windows 10 installation. Done means the GUI leaves "loading...", the logged-in tray interface is reliable, and KBFS is accessible.
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
- 20/100