Keybase fails to start the GUI under Fedora 35 on x86_64

[sergedroz]

Starting the Keybase guy fails under Fedora 35:

Version: 5.8.1-20210930160723+fefa22edc1 [15971:1113/072745.443511:FATAL:gpu_data_manager_impl_private.cc(442)] GPU process isn't usable. Goodbye. Trace/breakpoint trap (core dumped) The system has an nvidia card.

my log id: 4c16526b7297d0d14fb8d81c

[sergedroz]

The attached patch to keybase.gui.system allows you to start keybase, i.e. run

/opt/local/Keybase --no-sandbox

--- orig/keybase.gui.service	2021-11-19 19:16:58.574474490 +0100
+++ new/keybase.gui.service	2021-11-19 19:16:31.755727356 +0100
@@ -19,7 +19,7 @@
 EnvironmentFile=-%h/.config/keybase/keybase.autogen.env
 EnvironmentFile=-%h/.config/keybase/keybase.env
 
-ExecStart=/opt/keybase/Keybase
+ExecStart=/opt/keybase/Keybase --no-sandbox
 
 # After starting, we clear the KEYBASE_AUTOSTART variable so the next time
 # systemctl --start keybase.gui is called, it will be maximized.

[aanno]

I edited /usr/lib/systemd/user/keybase.gui.service like proposed on my f35 machine and the change circumvents the problem. Thanks!

[orgcontrib]

I hereby confirm the above workaround. Kudos to @sergedroz for sharing it.

[heronhaye]

What is the output of ls -la /opt/keybase/chrome-sandbox?

[heronhaye]

Actually, I believe this is due to an Electron bug. I will get a updated build out to test.

[sergedroz]

It would be: -rwsr-xr-x. 1 root root 4746192 Dec 17 22:43 /opt/keybase/chrome-sandbox

[heronhaye]

Sorry, I believe this is due to an upstream Electron issue that has not been fixed yet. We will upgrade Electron versions and release a new Keybase build when it is fixed.

[sergedroz]

https://www.reddit.com/r/Fedora/comments/qm3qm1/fedora_35_most_electron_apps_are_not_starting/ mentions a better workaround

--- orig/keybase.gui.service	2021-11-19 19:16:58.574474490 +0100
+++ new/keybase.gui.service	2021-11-19 19:16:31.755727356 +0100
@@ -19,7 +19,7 @@
 EnvironmentFile=-%h/.config/keybase/keybase.autogen.env
 EnvironmentFile=-%h/.config/keybase/keybase.env
 
-ExecStart=/opt/keybase/Keybase
+ExecStart=/opt/keybase/Keybase --disable-seccomp-filter-sandbox
 
 # After starting, we clear the KEYBASE_AUTOSTART variable so the next time
 # systemctl --start keybase.gui is called, it will be maximized.

This works and seems a safer option. The page also points to the electron bug in question (which is supposed to be fixed) https://github.com/electron/electron/pull/31091, not sure about that.

[orgcontrib]

I upgraded to F36, did a fresh install of Keybase, acknowledged issue still present. I revisited this thread, applied the better workaround above using one-line command.

uf=/usr/lib/systemd/user/keybase.gui.service; [[ -f $uf ]] && sudo sed -i 's,ExecStart=.*$,ExecStart=/opt/keybase/Keybase --disable-seccomp-filter-sandbox,' $uf || exit 1

GUI works fine after that. Again, thanks for sharing @sergedroz !

[SLoeuillet]

Same issue and same solution worked for me on Ubuntu 22.04 & release 5.9.3

(ansible) sloeuillet@sloeuillet-kaiko:~$ /opt/keybase/Keybase
Version: 5.9.3-20220216215910+c82d65a685
(node:1218310) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
(node:1218310) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
[1218310:0425/104401.462360:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
Trappe pour point d'arrêt et de trace (core dumped)

Adding --disable-seccomp-filter-sandbox worked

[heronhaye]

Hello all, please upgrade to Keybase 6.0.2. The workaround should not be necessary, but let me know if you run into issues. Thank you.

[Kaurin]

Fedora 37. I still have to use the --no-sandbox workaround even with 6.0.2

[socketbox]

@heronhaye

Using Keybase GUI Version: 6.0.2-20220610191041+a459abf326 and I'm still getting crashes:

1198 Mar 19 04:51:29 Deluxe Keybase[921278]: [921278:0319/045129.102803:ERROR:gpu_process_host.cc(979)] GPU process exited unexpectedly: exit_code=512
1199 Mar 19 04:51:42 Deluxe kernel: [734696.061614] show_signal: 91 callbacks suppressed
1200 Mar 19 04:51:42 Deluxe kernel: [734696.061620] traps: slack[1206391] trap int3 ip:55e7a7ff5a14 sp:7ffd08f273f0 error:0 in slack[55e7a4c68000+71c3000]
1201 Mar 19 04:51:44 Deluxe Keybase[921278]: [921278:0319/045144.110571:ERROR:gpu_process_host.cc(979)] GPU process exited unexpectedly: exit_code=512
1202 Mar 19 04:51:44 Deluxe Keybase[921278]: [921278:0319/045144.114099:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
1203 Mar 19 04:51:44 Deluxe kernel: [734697.572169] traps: Keybase[921278] trap int3 ip:56131cb71c73 sp:7ffc76e6c470 error:0 in Keybase[561319be1000+6af0000
1204 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Main process exited, code=dumped, status=5/TRAP
1205 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Failed with result 'core-dump'.
1206 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Unit process 921284 (Keybase) remains running after unit stopped.
1207 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Unit process 921285 (Keybase) remains running after unit stopped.
1208 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Unit process 921316 (Keybase) remains running after unit stopped.
1209 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Unit process 921320 (Keybase) remains running after unit stopped.
1210 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Unit process 921333 (Keybase) remains running after unit stopped.
1211 Mar 19 04:51:49 Deluxe systemd[2639]: keybase.gui.service: Consumed 1h 35min 17.528s CPU time.

I'm on Linux Mint 21.3 (Ubuntu 22.04) using the packaged .deb obtainable via curl --remote-name https://prerelease.keybase.io/keybase_amd64.deb