fusermount: entry for /run/user/1000/keybase/kbfs not found in /etc/mtab about kbfs

[eli-schwartz]

The run_keybase script is not very useful considering that it hardcodes the binary to start in /opt, whereas I package it in /usr/share and start it via /usr/bin/electron. And it also tries to run a redirector which I don't install, which runs as setuid root.

I'd need to reimplement the script, which I have not done since the only thing it currently does not do (to my knowledge) is mkdir -p "$(keybase config get -d -b mountdir)" -- hence my issue #1655 and corresponding PR.

If you create the directory by hand this works fine though. Even if you just start kbfs without the GUI. :p

[strib]

That fusermount command shouldn't be fatal, it's just trying to unmount an existing mount if there is one, before it tries to mount the new one. The error code should be ignored (it's prefixed with a - in the service definition).

If the FS really isn't working, there's probably something else going on later in the logs. You can try keybase log send and we can see if it's obvious from there.

I just sent my logs: 8006b217a7e06d16c361701c.

[strib]

The error is:

stat /run/user/1000/keybase/kbfs: no such file or directory

Looks like you might have the environment variable $XDG_RUNTIME_DIR set to /run/user/1000, but the OS didn't actually create that directory for you. Perhaps you are using su or sudo in an unusual way, and don't have a proper login session.

You can always change the mount directory with something like:

keybase config set mountdir /home/you/keybase

/run/user/1000/keybase/kbfs is the location I've come to expect. The /run/user/1000/keybase folder got created just fine.

Is setting the keybase mountdir to /home/me/keybase the recommended approach? Before switching from keybase-bin to keybase-gui, the "official" package was still using /run/user/1000/keybase.

[strib]

@miztroh2 did you start it with run_keybase? Or were you trying to start it purely via the service stuff? For now, run_keybase is required.

run_keybase doesn't seem to be included with the keybase-gui package (or its dependencies keybase and kbfs).

https://www.archlinux.org/packages/community/x86_64/keybase-gui/

[strib]

I'm not familiar with that package. @eli-schwartz ?

[eli-schwartz]

#1669

The run_keybase script has some annoying issues, including that kbfs.service does not even work on its own, plus it makes some fairly hard assumptions about how the electron app is packaged (note that the electron binaries provided by keybase are actually invalid machine code and don't run on glibc 2.28, while our electron binaries work fine).

So I've basically had to roll my own start script, and I've already reported the issue where kbfs depends on the GUI launch script in order to function.

[strib]

That's obviously not done yet. I thought the package included run_keybase. Did you take it out?

I stopped keybase.gui, keybase, and kbfs user services. I then manually created the kbfs folder inside of /run/user/1000/keybase and restarted said services. Everything checked out and I could access the kbfs mount through GNOME Files. However, once I restarted my computer, the kbfs directory was gone. Not sure what would cause that. Any ideas?

[eli-schwartz]

/run is a tmpfs and will be recreated from scratch at boot.

BTW my mountpoint is still set to ~/.local/share/keybase/fs (you can use keybase config set mountdir /path/to/custom/mountdir to relocate it at any time, and indeed it used to be there)

OK, I've updated my mountdir to the one you specified and that seems to work, even after reboot. Thanks!