Unable to stay persistently logged in on device

[zmanian]

▶ WARNING device id mismatch session <-> env ▶ WARNING device id mismatch session <-> env

I'm up to two of these errors from one before on "keybase login"

I've tried blowing away "~/.keybase"

I've tried "keybase logout".

Keybase GUI Version: 1.0.14-20160226170046+fe0b418

Linux Ubuntu 14.04

[maxtaco]

Hi @zmanian thanks for the feedback. Seems like a bunch of different things are going on. First off, for all Linux users reading this ticket, we strongly discourage nuking your ~/.config/keybase directory, for the simple reason that's where the only copy of your device secret keys are.

The ~/.keybase directory hasn't been in use for a very log time, that's from an early version of our node app that didn't even use the XDG layout. I'm guessing that didn't have much effect one way or the other.

The session in question is your API token used to authenticate your client to the keybase API server. It's a shared secret, so it's not really durable, we're happy to throw it away and start anew when it's called for.

Seems like you've been doing a fair number of device revokes, etc, so that could account for being in an unexpected state. Did you use the individual signature revoke subcommand, or did you revoke your device via keybase device revoke? Have you tried logging and and logging out?

[patrickxb]

One other suggestion I would have to attempt to fix your current state would be keybase ctl restart to restart the service daemon.

[ghost]

Sorry for hijacking this issue

The ~/.keybase directory hasn't been in use for a very log time, that's from an early version of our node app that didn't even use the XDG layout. I'm guessing that didn't have much effect one way or the other.

This means, it is safe to delete ~/.keybase entirely?

[maxtaco]

Yes, thanks for clarifying!

[zmanian]

So the device in question is a secondary device and I've been provisioning it via a Shared Secret from my primary device.

I've been running various versions of keybase on this machine since pretty early days. So there are lots of possibilities for inconsistent state.

It's currently ZakiBigDesktop in my device list.

I've tried the following flow.

keybase ctl restart keybase logout keybase login Choose option 1. Provision from exisiting key.

This flow succeeds and I get a keybase logged in notification.

Run "keybase status" and it tells me not logged in.

I'm thinking of blowing away .config/keybase but I'll wait on you to tell me if you want some additional forensics.

Let me know if there is anything else I can do to help.

This is my office desktop so I don't always have access to it.

[zmanian]

I backed up .config/keybase. I also had .config/Keybase directory that had Electron related artifacts in it.

I backed both up and then re provisioned the device.

I'm able to stay logged in now/

[fenixnet-net]

I'm having the same issue. I commented on https://github.com/keybase/client/issues/2463 as well, but I'll add here since it's related.

I log in and cannot reclaim the device name. Create a new one, verify, client says great. Then I try to do decrypt and client says I'm not logged in. Repeat forever, burning device names as I go.

keybase login result: "✔ Success! You provisioned your device laptop. You are logged in as jadefalcon1"

keybase decrypt "▶ ERROR No device found for device ID 17018c9dbb99299e0d9abe6984e56818"

keybase log send "▶ WARNING error opening log "/Users/cameron/Library/Logs/keybase.kbfs.log": open /Users/cameron/Library/Logs/keybase.kbfs.log: no such file or directory ▶ WARNING error opening log "/Users/cameron/Library/Logs/Keybase.app.log": open /Users/cameron/Library/Logs/Keybase.app.log: no such file or directory" Log ID afd75fbae42bd134c4d3021c

keybase status "▶ WARNING device id mismatch session <-> env Username: jadefalcon1 Logged in: no Session: jadefalcon1 [salt only] is valid: no keys: locked lksec: loaded

KBFS: status: not running version:

log: /Users/cameron/Library/Logs/keybase.kbfs.log

Service: status: running version: 1.0.15 log: /Users/cameron/Library/Logs/keybase.service.log

Platform Information: OS: darwin Runtime: go1.6 Arch: amd64

Client: version: 1.0.15

Desktop app: status: not running version:

log: /Users/cameron/Library/Logs/Keybase.app.log

Config path: /Users/cameron/Library/Application Support/Keybase/config.json Default user: jadefalcon1 Other users:

command-line client: keybase status [pid: 74401, version: 1.0.15]"

[fenixnet-net]

Great, thank you. I can still do stuff via the website and my linux box so I'm not totally blocked.

[maxtaco]

Sorry, I deleted that comment, since I didn't realize it's the same person in both threads.

[fenixnet-net]

No worries.