The first time I try to run 2026.4.0 flatpak app on Fedora 44, the first time it fails right after the screen is rendered throwing the error below:
...
22:32:39.944 › Migrator MigratePopupWidthOptions (to version 76) should migrate: false - up
22:32:39.944 › Migrator ClearClipboardDelayToStringMigrator (to version 77) should migrate: false - up
Gtk-Message: 22:32:39.990: Failed to load module “canberra-gtk-module”
Gtk-Message: 22:32:39.990: Failed to load module “pk-gtk-module”
Gtk-Message: 22:32:39.991: Failed to load module “canberra-gtk-module”
Gtk-Message: 22:32:39.991: Failed to load module “pk-gtk-module”
22:32:40.031 › [Process Isolation] Isolating process from debuggers and memory dumps
22:32:40.035 › [NAPI] [INFO] desktop_core::process_isolation::process_isolation: Disabling ptrace and memory access for main via PR_SET_DUMPABLE. pid=2
22:32:40.060 › Coredumps are disabled in renderer process
LaunchProcess: failed to execvp:
xdg-settings
22:32:40.175 › [NAPI] [INFO] desktop_core::autostart::autostart_impl: [ASHPD] Autostart enabled response=Background { background: true, autostart: true }
22:32:40.470 › [Native Messaging IPC] Clearing connected apps
Error occurred in handler for ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
at Session. (node:electron/js2c/browser_init:2:112875)
at Session.emit (node:events:519:28)
22:32:40.478 › State version: 77
22:32:40.478 › Unhandled error in angular Error: Error invoking remote method ‘sshagent.clearkeys’: Error: No handler registered for ‘sshagent.clearkeys’
22:32:40.538 › Using SignalR for server notifications
22:32:41.488 › [SignalR] WebSocket connected to wss://notifications.bitwarden.com/hub?access_token=[REDACTED]
22:32:41.488 › [SignalR] Using HubProtocol ‘messagepack’.
(the Gtk-Messages seem to be harmless)
After this error, the app is still running, though, and the second attempt to run it succeeds. Quitting this app with CTRL+Q also makes the first app (now running in the background only) quit, with exit code 0 (success). From now on, the above pattern keeps repeating: first attempt immediately closes the GUI but keeps running in the background, second attempt succeeds but gracefully terminates first app when it exits.
AFAIK this was introduced with 2026.4.0.
