Open mshron opened 8 years ago
Try keybase unlock --stdin
? Normally the problem is that you haven't unlocked your device private key, and there's no GUI to prompt you for that. But @cjb has more experience than I do with this.
The very bottom of the KBFS log eventually shows logged in progress followed by a hang.
@cjb: that's not progress. Looks like the user canceled an operation that was waiting on the exponential backoff algorithm to try again. I don't see any successful authentication.
Oops. Thanks, I agree.
I've had a similar issue on my Chromebook, trying to view files in /keybase/public/jamgregory
after running run_keybase
. I'm guessing it hadn't unlocked, and so hung at that point. After I ran keybase unlock
, it seemed to work OK.
[write something useful and descriptive here]
my log id: 0f979c7bc8410eda7a02c01c