'keybase login' says I'm logged in but 'keybase status' disagrees

[bortzmeyer]

% keybase login
How would you like to sign this install of Keybase?

(1) Use an existing device
(2) Use a paper key
(3) Use my Keybase passphrase
Choose a signing option: 1
What is your existing device?

(1) Desktop or laptop
(2) Mobile phone

Choose a device type: 1
Type this verification code into your other device:

    NOT SHOWN

If you are using the command line client on your other device, run this command:

    keybase device add

It will then prompt you for the verification code above.

Enter a public name for this device: mononoke2
✔ Success! You provisioned your device mononoke2.

You are logged in as bortzmeyer
  - type `keybase help` for more info.

But:

% keybase status
Username:      bortzmeyer
Logged in:     no
Local keybase keychain: locked
Session status:         bortzmeyer [salt only]

KBFS:
    status:    not running
    version:   
    log:       /home/stephane/.cache/keybase/keybase.kbfs.log

Service:
    status:    running
    version:   1.0.11-20160212170047+3050b64
    log:       /home/stephane/.cache/keybase/keybase.service.log

Platform Information:
    OS:        linux
    Runtime:   go1.5.3
    Arch:      amd64

Client:
    version:   1.0.11-20160212170047+3050b64

Desktop app:
    status:    not running
    log:       /home/stephane/.cache/keybase/Keybase.app.log

Config path:        /home/stephane/.config/keybase/config.json
Default user:       bortzmeyer
Provisioned users:  

command-line client(s):
    keybase status [pid: 22994, version: 1.0.11-20160212170047+3050b64]

So, it seems I'm not logged in

my log id: 618de189612eb6863e8f6e1c

[patrickxb]

Hi Stéphane,

I looked through your log. It does look like you provisioned successfully and I can see the devices for you. I'm trying to track down the bug and my current theory is that the service did not get your updated config values after provisioning or lost them.

It looks like the file was written correctly in the log, so I just wanted to confirm that. Can you look in /home/stephane/.config/keybase/config.json and tell me if you have a section like this:

"users": {
    "bortzmeyer": {
        "device": "000000....",
        "id": "0000000....",
        "name": "bortzmeyer",
        "salt": "0000000...."
    }
}

If so, I think keybase ctl restart followed by keybase login should work. The keybase login should not result in device provisioning and afterwards keybase status should show you as logged in.

I will be trying to reproduce this locally, but it would help if you could tell me the status of your config.json file.

Thanks!

[bortzmeyer]

On Mon, Feb 15, 2016 at 12:48:58PM -0800, Patrick Crosby notifications@github.com wrote a message of 90 lines which said:

Hi Stéphane,

Hi (sorry for the delay, interrupted by $DAYWORK)

It looks like the file was written correctly in the log, so I just wanted to confirm that. Can you look in /home/stephane/.config/keybase/config.json and tell me if you have a section like this:

Not exactly like this. I have:

% cat /home/stephane/.config/keybase/config.json

{ "current_user": "bortzmeyer", "updates": { "last_checked": "1455381316913" }, "users": { "bortzmeyer": { "device": null, "id": "01323bf91cdb8736ef01f1246170f900", "name": "bortzmeyer", "salt": "b453b87b526535db86417d8a91d7e208" } } }

If so, I think keybase ctl restart

% keybase ctl restart ▶ INFO Delaying for shutdown...

▶ INFO Restart ▶ INFO Forking background server with pid=2158

followed by keybase login should work.

No:

% keybase login ▶ WARNING Session file found but user is not logged in. Deleting session file. How would you like to sign this install of Keybase?

(1) Use an existing device (2) Use a paper key (3) Use my Keybase passphrase Choose a signing option: