"Transport endpoint is not connected" while upgrading deb package

[eppesuig]

Hello,
quite often I issue the command apt dist-upgrade on my Debian Trixie box, but since a few months, everytime I upgrade all packages, I get an error with keybase. This is the error transcript:

# LC_ALL=C LANG=C dpkg --configure --pending
Setting up keybase (6.2.8-20240306193933.e38523abbe) ...
Autorestarting Keybase via systemd for giuseppe.
mkdir: cannot stat '/keybase': Transport endpoint is not connected
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

The /keybase path seems to be a mountpoint, indeed:

# mount | grep keybase
keybase-redirector on /keybase type fuse (ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /run/user/1000/keybase/kbfs type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

The keybase system services are active:

# systemctl status keybase.mount keyboard-setup.service run-user-1000-keybase-kbfs.mount
● keybase.mount - /keybase
     Loaded: loaded (/proc/self/mountinfo)
     Active: active (mounted) since Thu 2024-03-07 09:04:12 CET; 24h ago
      Where: /keybase
       What: keybase-redirector

● keyboard-setup.service - Set the console keyboard layout
     Loaded: loaded (/usr/lib/systemd/system/keyboard-setup.service; enabled; preset: enabled)
     Active: active (exited) since Mon 2024-03-04 09:11:15 CET; 3 days ago
   Main PID: 494 (code=exited, status=0/SUCCESS)
        CPU: 6ms

● run-user-1000-keybase-kbfs.mount - /run/user/1000/keybase/kbfs
     Loaded: loaded (/proc/self/mountinfo)
     Active: active (mounted) since Fri 2024-03-08 09:02:06 CET; 5min ago
      Where: /run/user/1000/keybase/kbfs
       What: /dev/fuse

Notice: journal has been rotated since unit was started, output may be incomplete.

Checking the user services for user giuseppe (the original error message seems about that user), I see:

$ systemctl --user --no-pager status keybase.mount run-user-1000-keybase-kbfs.mount keybase.gui.service keybase.service
● keybase.mount - /keybase
     Loaded: loaded (/proc/self/mountinfo)
     Active: active (mounted) since Fri 2024-03-08 08:52:48 CET; 18min ago
      Where: /keybase
       What: keybase-redirector

● run-user-1000-keybase-kbfs.mount - /run/user/1000/keybase/kbfs
     Loaded: loaded (/proc/self/mountinfo)
     Active: active (mounted) since Fri 2024-03-08 09:02:06 CET; 9min ago
      Where: /run/user/1000/keybase/kbfs
       What: /dev/fuse

● keybase.gui.service - Keybase GUI
     Loaded: loaded (/usr/lib/systemd/user/keybase.gui.service; static)
     Active: active (running) since Fri 2024-03-08 09:02:06 CET; 9min ago
    Process: 639882 ExecStartPost=/usr/bin/env systemctl --user unset-environment KEYBASE_AUTOSTART (code=exited, status=0/SUCCESS)
   Main PID: 639880 (Keybase)
      Tasks: 79 (limit: 14187)
     Memory: 570.1M (peak: 820.4M)
        CPU: 4.993s
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/keybase.gui.service
             ├─639880 /opt/keybase/Keybase
             ├─639891 "/opt/keybase/Keybase --type=zygote --no-zygote-sandbox"
             ├─639892 "/opt/keybase/Keybase --type=zygote"
             ├─639903 "/opt/keybase/Keybase --type=zygote"
             ├─639929 "/opt/keybase/Keybase --type=gpu-process --enable-crash-reporter=7820fe1c-abe2-46af-8ad5-e3b5268f2b73,no_channel --user-data-dir=/home/giuseppe/.config/Keybase --gpu-p…
             ├─639934 "/opt/keybase/Keybase --type=utility --utility-sub-type=network.mojom.NetworkService --lang=it --service-sandbox-type=none --enable-crash-reporter=7820fe1c-abe2-46af-8…
             ├─639937 "/opt/keybase/Keybase --type=renderer --enable-crash-reporter=7820fe1c-abe2-46af-8ad5-e3b5268f2b73,no_channel --user-data-dir=/home/giuseppe/.config/Keybase --app-path…
             └─639945 "/opt/keybase/Keybase --type=renderer --enable-crash-reporter=7820fe1c-abe2-46af-8ad5-e3b5268f2b73,no_channel --user-data-dir=/home/giuseppe/.config/Keybase --app-path…

mar 08 09:02:06 supergulp.ion.lixper.local systemd[623029]: Starting keybase.gui.service - Keybase GUI...
mar 08 09:02:06 supergulp.ion.lixper.local systemd[623029]: Started keybase.gui.service - Keybase GUI.
mar 08 09:02:06 supergulp.ion.lixper.local Keybase[639880]: Version: 6.2.8-20240306193933+e38523abbe
mar 08 09:02:06 supergulp.ion.lixper.local Keybase[639880]: RPC [I] localhost: connection established
mar 08 09:02:07 supergulp.ion.lixper.local Keybase[639929]: MESA-INTEL: warning: Haswell Vulkan support is incomplete
mar 08 09:02:07 supergulp.ion.lixper.local Keybase[639929]: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
mar 08 09:02:10 supergulp.ion.lixper.local Keybase[639929]: [639929:0308/090210.431542:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
mar 08 09:02:10 supergulp.ion.lixper.local Keybase[639929]: [639929:0308/090210.463637:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
mar 08 09:02:10 supergulp.ion.lixper.local Keybase[639929]: [639929:0308/090210.473104:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

● keybase.service - Keybase core service
     Loaded: loaded (/usr/lib/systemd/user/keybase.service; disabled; preset: enabled)
     Active: active (running) since Fri 2024-03-08 09:02:05 CET; 9min ago
   Main PID: 639780 (keybase)
      Tasks: 11 (limit: 14187)
     Memory: 198.7M (peak: 229.2M)
        CPU: 5.423s
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/keybase.service
             └─639780 /usr/bin/keybase --use-default-log-file --debug service

mar 08 09:02:05 supergulp.ion.lixper.local systemd[623029]: Starting keybase.service - Keybase core service...
mar 08 09:02:05 supergulp.ion.lixper.local systemd[623029]: Started keybase.service - Keybase core service.

So, the only error I see is about the GUI service that complains on a Video Acceleration library initialization failing. Is this really the problem source?

If that is the root cause, here is some more information about my system:

$ vainfo --display drm --device /dev/dri/renderD128 
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.20 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Server - 2.4.1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      :	VAEntrypointVLD
      VAProfileH264MultiviewHigh      :	VAEntrypointEncSlice
      VAProfileH264StereoHigh         :	VAEntrypointVLD
      VAProfileH264StereoHigh         :	VAEntrypointEncSlice
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileJPEGBaseline           :	VAEntrypointVLD

Thank you,
Giuseppe

[robyf]

I had a very similar issue and it got resolved by running sudo fusermount -u /keybase and then apt upgrade to finalize the installation. No idea why though.

[eppesuig]

Thanks, but this seems not to be working in my case. I get error message: fusermount: failed to unmount /keybase: Device or resource busy

[wom-bat]

Thanks, but this seems not to be working in my case. I get error message: fusermount: failed to unmount /keybase: Device or resource busy

Yes I see that too.
FIx is

sudo umount -f /keybase

I'm also seeing hangs whenever I access /keybase/

[wom-bat]

OK, so I've been playing around a bit. If I kill keybase-redirector and restart it after I've started the keybase client, then all is good.

If the keybase-redirector process starts before the keybase client, then any attempt to access the mounted directory hangs