Unable to access K: drive

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron

BSD 3-Clause "New" or "Revised" License

8.88k stars 1.23k forks source link

Unable to access K: drive #11466

Open nilskp opened 6 years ago

nilskp commented 6 years ago

my log id: eb25cde6e0cbbee056217a1c

kbfs

strib commented 6 years ago

cc: @zanderz

zanderz commented 6 years ago

@nilskp Can you please try one or both of the following tests:

Uncheck "Open Keybase on startup" in the Settings tab under Advanced, then reboot. or
Temporarily remove %AppData%\Microsoft\Windows\Start Menu\Programs\Startup\KeybaseStartup.lnk, then reboot

In either case, does your drive mount work? how about after starting the Keybase app? Thanks.

nilskp commented 6 years ago

I restarted my PC, and it was back to working, however, this should not be necessary, correct? Was the log helpful in preventing this in the future? Also, I now find it frightening that I cannot access a local copy, if something, anything, is wrong. I've never had that problem with OneDrive.

zanderz commented 6 years ago

@nilskp Did you change settings or remove the startup link before rebooting to get it working? The case I am attempting to debug is whether the startup link and the GUI startup have a timing conflict in certain situations.

If you are logged in to Keybase, you can always access kbfs files with the CLI via keybase fs commands.

nilskp commented 6 years ago

@zanderz no, I didn't do either of those things.

stephlocke commented 6 years ago

I'm getting this issue (winbuild 1709 and Keybase GUI Version: 1.0.47-20180404145836+0fe66b9) where keybase becomes inaccessible if it starts up or unlocks without internet. Usually quitting keybase and running it again works. I've removed it from startup but needing to kill it after each unlock on many wifi connections is difficult.

logid cd61be74daa44e80cb18c61c