'keybase login' says I'm logged in but 'keybase status' disagrees
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
```
% 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
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the mismatch with `keybase login` and `keybase status` using the captured output and log id 618de189612eb6863e8f6e1c. Compare the login, keychain, session, and provisioned-user states; done when status accurately reflects the successful login or clearly reports why it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100