kbfs frozen, cannot manipulate with files about kbfs HOT 12 CLOSED

Can you please do a keybase log send and let us know the resulting log ID? Thanks.

from kbfs.

@strib 7fac560793d413d82313871c Thanks for a quick response.

from kbfs.

It seems like your local device key hasn't been unlocked. Maybe you pressed cancel on a passphrase entry dialogue? (Or maybe there is a popup window you haven't noticed somewhere?)

If not, maybe try an explicit keybase unlock (or keybase logout followed by keybase login) and see if that helps?

from kbfs.

When I restarted the system earlier, I could see a plain white window without decoration with the keybase icon. I closed it. I can access the keybase application from the system tray just fine, though.
I tried all of keybase unlock/logout/login, they all freeze and I have to interrupt it using ctrl+c.
I wanted to send another log, but now even the keybase log send command is frozen, after I typed "YES".

from kbfs.

Oh, seems like another plain white window appeared. That might be blocking keybase from functioning.

from kbfs.

Ran killall keybase and restarted keybase log send, if that helps. 8048851fa0ba201a0258de1c

from kbfs.

cc @cjb @gabriel for plain white pinentry windows. Sorry for the inconvenience!

from kbfs.

@Limeth by the way, keybase unlock takes a --stdin parameter, letting you type your passphrase in the terminal instead of a GUI window (or letting you pipe it in from a file). Not sure if that will solve your issue but it's worth a try.

from kbfs.

Running keybase unlock (with or without --stdin) gives me this error:

▶ ERROR dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory

from kbfs.

(deleted my previous comment since this is linux)

@oconnor663 Do we have a recent linux build with this fix?

from kbfs.

@gabriel a new build went out on Linux about two hours after your comment yesterday.

from kbfs.

Updated keybase, everything seems to be working again.

from kbfs.