Keybase will not open to desktop

[GitMarkalsoHub]

I am getting "starting up keybase" continuously

my log id: 8aea9555fb483812a7400a1c

[123Venom]

Same here. Uninstall/Re-Install did nothing to fix this either.

log id: e10b4a72b3f2101ed851e91c

[GitMarkalsoHub]

Yes, I did the uninstall and reinstall also. Did the same thing.

…

On Fri, Jun 10, 2022 at 11:39 AM Venom ***@***.***> wrote: Same here. Uninstall/Re-Install did nothing to fix this either. — Reply to this email directly, view it on GitHub <#25050 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEAHVNJHQMAGNH7YZHLTOA3VONVVLANCNFSM5YN6INAA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MaxQuatro]

Avast reported about keybaserq.exe as FileRepMalware [Trj].

[123Venom]

Something very strange I just noticed. While on Win10 keybase sits in the show hidden icons tray as Starting up keybase but if I attempt to launch another instance of \AppData\Local\Keybase\Gui\Keybase.exe that then allow the login screen all while that other instance sits with Starting up keybase. Something in 6.0.1 deff messed things up.

[Mykola-Veryha]

I just updated to 6.0.2 and now it works well for me

[GitMarkalsoHub]

Where is the Windows 6.02 update URL? I have gone to the website and I am only seeing 6.02 version for Linux

[123Venom]

I installed latest today on win10 and received V6.0.1.49 so I'm in the same boat wondering where v6.0.2 came from? That 6.0.1.49 did not fix the issue for me. I still get an instance in the try "Starting up keybase". The only way I can get it to work is launch a new instance.

[rdavies3]

Same issue on a mac. Upgraded this morning, my log ID is 1e7d4435dc894d2e7c84061c

[123Venom]

Lot of issues being reported of having this problem. Be nice to see it fixed.

[123Venom]

2 weeks later still not fixed nor a response on the matter.

[ec-max]

Sounds like the behavior I fixed here: #25138 (comment)

[123Venom]

That's all fine if you are setup to start kb on windows start, I was not. I tested this by closing kb. Attempted a manual run with the short name version of the user. It still does the same thing. The first instance is blank and sits forever on starting up keybase. If I open a 2nd instance that one then works but that whacky tray instance must remain.

[ec-max]

Sorry for the false hope. You describe the exact same behavior I was seeing on a fresh install (new machine): First run whacky tray instance wasn't working, second copy worked fine. Even installed the KBFS support and that mounted up fine with my account/data mounted as a drive letter; but not the whacky first instance tray copy; until I eliminated spaces from the path. I haven't had to go experiment with this; but looking at the client source files, it is reading from %LOCALAPPDATA% - which has the space included long file name in the environment variable. If you are still having the issue you may get somewhere by setting that variable to the short filename too. Worth 5 minutes to try anyway. ?shrug?