client: GUI and KBFS bugs in 5.9.0 on Windows and Linux

Since upgrading to 5.9.0 on Windows 11, keybase does not fully start. The GUI is stuck on a Loading message and kbfs is not mapped to K: or any other drive letter. This would seem to be the same issue as reported in https://github.com/keybase/client/issues/24745 and https://github.com/keybase/keybase-issues/issues/4087.

I have also experienced a similar issue using the linux client (for debian-based systems). Upon upgrading to 5.9.0, kbfs would not cleanly mount at /keybase, though the GUI did seem to work as expected, and I found my keybase files could be accessed at /run/user/<uid>/keybase/kbfs.

On linux I was able to downgrade to 5.8.1 and set an apt hold to prevent re-upgrading to 5.9.0.

my log id: 23ad4baebe37f3d92088101c

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 6
  • Comments: 44 (7 by maintainers)

Most upvoted comments

@karlvlam, @tgockel, @sc6l6d3v, and all others having issues, please try out the latest 5.9.3 test build:

.deb: https://s3.amazonaws.com/tests.keybase.io/linux_binaries/deb/index.html .rpm: https://s3.amazonaws.com/tests.keybase.io/linux_binaries/rpm/index.html

A restart might be required before/after installing.

You can verify the signature on the binary against our code signing key at https://book.keybase.io/docs/server/our-code-signing-key.

I’m hoping this will resolve the issues, especially with ls / hanging. If you are still having issues, let me know. Otherwise I will promote this test build to a release in a few days. Thanks for your patience.

When I downgrade to keybase version 5.8.1-20210930160723+fefa22edc1, journalctl gives me identical output after reboot, except for the blocked tasks reported by the kernel at the end. Not many clues here I’m afraid, but everything works again, in the terminal I can navigate to the root of the file system, run ls and it won’t hang.

Where is the repo to find this old version or did you do this solely through the platform installer as a downgrade?

https://github.com/keybase/client/issues/24749#issuecomment-998906626

@orgcontrib re:

It’s always better to use/update existing tickets (search through active/open issues before creating a new one).

Understood, however

  1. The issue you linked did not appear in my searches,
  2. These appeared to be emergent bugs in release 5.9.0 (I am a long-time user of KB on multiple platforms and have not previously seen these behaviors), and
  3. Upon completing keybase log send, the output suggested creating a new issue in this queue that included the log ID submitted.

Note: For debian-based installations, here is the workaround to downgrade, for those who may be interested…

  1. Go to https://prerelease.keybase.io/ and then click the linux/deb link
  2. Download the version 5.8.1 .deb file appropriate for your system (ie. the *i386.deb file for 32-bit systems or the *amd64.deb for 64-bit systems). Optionally (preferably) also download the corresponding PGP signature and verify the downloaded .deb file
  3. Run sudo apt purge keybase to remove version 5.9.0. You may need to reboot at this point (on one system I needed to do so to cleanly install 5.8.1 but not an another)
  4. Run sudo apt-get install /path/to/<keybase 5.8.1 deb file>
  5. Set an upgrade hold on keybase to prevent re-upgrading to 5.9.0: sudo apt-mark hold keybase