ls: cannot access '/keybase': Transport endpoint is not connected

[jirib]

Describe the bug

I cannot access files from CLI at /keybase, however it seems /run/user/<user>/keybase/kbfs shows the files - Debian unstable 6.4.0-20240821175720.3212f60cc5 (I tried also nightly, the same); however, during the installation there was some warnings:

Warning: program compiled against libxml 212 using older 209

jiri@t14s:~$ findmnt | grep keybase
│   ├─/run/user/1000/keybase/kbfs                               /dev/fuse                 fuse            rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
└─/keybase                                                      keybase-redirector        fuse            ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other

jiri@t14s:~$ ls -l /run/user/1000/keybase/kbfs/private/jirib79/ /keybase/private/jirib79/
ls: cannot access '/keybase/private/jirib79/': Transport endpoint is not connected
/run/user/1000/keybase/kbfs/private/jirib79/:
total 2
-rw-------. 1 jiri root 1036 Oct  3 13:17 fstab

To Reproduce
Steps to reproduce the behavior:

1. Debian Unstable
2. deb package
3. run_keybase
4. ls /keybase/private/<user>

Expected behavior

Files should be visible.

Additional numbers
The number 345567

[jamgregory]

I've just noticed the same thing on Ubuntu 20.04 with the same version (6.4.0-20240821175720.3212f60cc5)

[Johnson1s]

Same

[pocoraven]

This is happening on Arch as well. Closing the client (while still having it in the systray) will cause / to become inaccessible. A restart temporarily fixes this issue.

You HAVE to keep the window open. No exceptions. If you close it, keybase has a stroke. That's my best explanation.