Open RileyStarlight opened 2 years ago
Had the same issue. Used fusermount -u /keybase
to unmount the fuse "device". Killed keybase and then ran apt autoremove
just to test it out. apt
came back with the following:
[2022-01-30 11:47:01]» apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
libstd-rust-1.51
0 upgraded, 0 newly installed, 1 to remove and 7 not upgraded.
1 not fully installed or removed.
After this operation, 149 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 654962 files and directories currently installed.)
Removing libstd-rust-1.51:amd64 (1.51.0+dfsg1+llvm-1~exp3ubuntu1~18.04.1) ...
Setting up keybase (5.9.0-20220120174718.95a3939b3a) ...
Autorestarting Keybase via systemd for chb.
Restarted existing root redirector via systemd.
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
W: APT had planned for dpkg to do more than it reported back (3 vs 7).
Affected packages: keybase:amd64
I can't find anything using dpkg
or apt
that would indicate why keybase is treated as relevant in invocation of apt
. The package is seen as installed and not broken.
Potentially related: https://github.com/keybase/client/issues/24764
I guess I'm having the same issue but with keybase 5.9.3:
marcelo@marcelo-thinkpad:~$ LANG=C sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up keybase (5.9.3-20220216215910.c82d65a685) ...
Autorestarting Keybase via systemd for marcelo.
mkdir: cannot create directory '/keybase': File exists
chown: cannot access '/keybase': Transport endpoint is not connected
chmod: cannot access '/keybase': Transport endpoint is not connected
dpkg: error processing package keybase (--configure):
installed keybase package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
keybase
E: Sub-process /usr/bin/dpkg returned an error code (1)
marcelo@marcelo-thinkpad:~$ LANG=C ls -alh / | grep keybase
ls: cannot access '/keybase': Transport endpoint is not connected
d????????? ? ? ? ? ? keybase
The app works fine, tough. I'm running Ubuntu 20.04.3 fully updated. What can I do to add more info?
The package remains as partially installed, and keybase services are restarted with each apt run.
However, the application seems to update and launches correctly. The
/keybase
mount folder becomes corrupted?Keybase version: 5.9.0-20220120174718+95a3939b3a OS: Linux Mint 19.3