Windows client failing to mount KBFS or show devices when started manually
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Log ID: 2d3c0d7be100e14c6b8d721c
Running on Windows 7 Professional as an authenticated user in an AD environment.
I removed Keybase shortcuts from my startup folder. I don't need them to be running all the time, and being prompted for a password at login (long before my password manager is online) was inconvenient.
Now I'm attempting to start Keybase/KBFS, but it isn't mounting K: (the drive letter remains unassigned). In addition, the Keybase GUI is not showing any devices:
The CLI client is showing active, logged in and unlocked when running keybase status. Additionally, keybase device list is listing my devices.
The system tray icon is working, and showing my public and private folders, including known shared folders. It is unable to launch them in explorer, but isn't giving any error messages. "Report a Bug" isn't working.
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 report names no source files or tests. Start by reproducing the manually started Windows 7 case, checking keybase status and keybase device list, then trace the Windows startup, KBFS mount, and GUI device-display entry points. Done means the client mounts K:, shows devices, and opens the listed folders in Explorer when started manually.
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