Expired session after adding new device

Found some oddity in how keybase sets up on a 2nd device. I think. :)

The situation:

• Keybase set up and working fine on local machine and used often.
• I was trying to get a secondary machine, a VPS, access to my keybase filesystem.
• 2nd machine is headless (no UI). Not sure if this is a factor.
• Installed keybase on second machine.
• keybase device add -- added second machine.
• ls /keybase/public// --- sits there forever.
• run_keybase
• ls /keybase/public -- shows my username
• ls /keybase/public// --- sits there forever.
• keybase login -- I login thinking maybe there is a dialogue box that I am not seeing.
• ls /keybase/public// --- sits there forever.
• keybase status -- I see nothing obvious, but I save the output
• keybase unlock
• ls /keybase/public// --- WORKS!
• keybase status -- save new output and diff...

-Session:       toddwarner [loaded: yes, cleared: no, expired: no]
+Session:       toddwarner [loaded: yes, cleared: no, expired: yes]

Now why would the session be expired right off the bat? I even rebooted to see if that would remedy things auto-magically. It did not. I had to manually unlock things.

Anyway. It smells like there is a bug here somewhere. Or at least, a sub-optimal workflow. I hope this helps.

my log id: 3b091934cdac5a9bb3ec921c

Start by reproducing the documented headless second-device command sequence, especially keybase device add, keybase login, keybase unlock, and keybase status, and inspect log id 3b091934cdac5a9bb3ec921c. Done means identifying why the session is initially marked expired and confirming that the workflow no longer requires a manual unlock before filesystem access.