oconnor663
commented
8 years ago It looks like you've done at least a couple account resets since provisioning your Linux machine. So the client is right to tell you that the device doesn't exist. You'll need to do a keybase login on that machine again before you'll be able to use the client there. (We need a "this used to be a valid device but then you did an account" reset error message for this case. Sorry for the confusion.)
Because of an unrelated server bug, we don't clear out the people you track when you do an account reset. So what you see on your page shows more people than what's actually in your sigchain post-reset.
I tried to recreate pub/private key for use with Keybase.io, using keybase gen (on OSX El Capitan) and keybase pgp gen (on Ubuntu 14.04.3 LTS, keybase version 1.0.0-46). But now I cannot remove people that I'm tracking(error: You're not tracking 'jkakar', even though my page says I am). Also I can't generate paperkey on Linux, getting the error 'ERROR No device found No device found for device ID fadecbca...). The Linux box used to be on the device list before I had to recreate the keys, so that may have caused some issues. I tried using 'keybase reset' on the Linux box, also tried 'dpkg -P keybase', but nothing helped. When I check with 'keybase device list', no devices show. On OSX (running node v5.0.0, keybase version 0.8.23), I also cannot untrack, getting the same error as on Linux box.