Windows client does not handle over-mounting K: drive
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.29-20170906185616+0c0bb88
First time install of Keybase. Did not realize it mounts to K:. Went ahead and mounted a VeraCrypt volume to K:, because that's what I have always done, and Keybase did not realize what happened. Ideally it would detect that its drive has been unmounted and notify the user about this fact and suggest a way to correct it. Instead, it simply asks me to repair the installation. If you select "Repair", it can't find an .exe and opens a browser asking you to find it. I may have to reinstall.
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
No source file, test, or entry point is identified in the issue. Start by reproducing the Windows client behavior after another volume is mounted over K:, then trace the handling of the missing or inaccessible Keybase drive; done means the client reports the over-mounting clearly and offers a corrective path instead of directing the user to repair an unavailable executable.
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
- Mostly clear
- Newbie friendliness
- 35/100