Open dhgwilliam opened 8 years ago
Oh dear. Would you please move your ~/.local/share/keybase/keybase.leveldb
folder to ~/keybase-broken-leveldb
or something (rather than deleting it, so that we have the option of restoring it or looking at it later)? Any chance that just fixes the problem?
I actually rectified the situation myself. Left bug open in case there was a UX lesson here ☺
Are there any logs that might be helpful?
On Wed, Feb 10, 2016, 5:49 PM oconnor663 notifications@github.com wrote:
Oh dear. Would you please move your ~/.local/share/keybase/keybase.leveldb folder to ~/keybase-broken-leveldb or something (rather than deleting it, so that we have the option of restoring it or looking at it later)? Any chance that just fixes the problem?
— Reply to this email directly or view it on GitHub https://github.com/keybase/client/issues/1967#issuecomment-182670366.
Thanks. Do you happen to remember what you were doing when the corruption first showed up?
I believe I misplaced my device key password and manually destroyed the GUI window hoping to restart the login process but I think keybase lost track of where it was and tried to proceed as though I had entered the password correctly. After that I was unable to provide any passwords or login at all due to db corruption.
I may have accidentally avoided entering the passphrase for my paper key?
my log id: 3e6e024a73f273352d23e71c