KeePassXC not opening on new fresh baremetal installation

As title says, new installation on thinkpad x560, i even downloaded the appimage from their site, it wont open either. Opens fine inside vbox on my home pc so its a laptop problem as far as i know.

hmm if the appimage wont open either its probably not the flatpak/package itself. in my experience on thinkpads that usually ends up being a missing qt/xcb lib or the app crashing on start before any window shows.

maybe try from a terminal:
keepassxc
or the appimage path, and see what error dumps out

also journalctl --user -xe right after a failed launch sometimes shows the qt plugin / libxcb thing. if its a black box with no error, QT_DEBUG_PLUGINS=1 can be noisy but useful.

probably not kicksecure-specific if vbox works, more like the bare metal session libs.

OK it gets more ridiculous. KeePass works on that laptop INSIDE both kicksecure and whonix vm’s

When i try from terminal it spits error
zsh: illegal hardware instruction (core dumped) keepassxc

journalctl --user -xe
Spits this

Sep 04 09:20:47 localhost gnome-keyring-daemon\[4149\]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Sep 04 09:20:47 localhost dbus-daemon\[2859\]: \[session uid=1000 pid=2859 pidfd=5\] Successfully activated service 'org.freedesktop.secrets'
Sep 04 09:20:47 localhost gnome-keyring-daemon\[4149\]: The Secret Service was already initialized
Sep 04 09:20:47 localhost gnome-keyring-d\[4149\]: The Secret Service was already initialized
Sep 04 09:20:47 localhost gnome-keyring-daemon\[4146\]: discover_other_daemon: 1
Sep 04 09:20:47 localhost org.freedesktop.secrets\[4146\]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Sep 04 09:20:47 localhost dbus-daemon\[2859\]: \[session uid=1000 pid=2859 pidfd=5\] Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.53' (uid=1000 pid=4149 comm="/usr/bin/gnome-keyring->
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: bus acquired: org.gnome.keyring.SystemPrompter
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: registering prompter
Sep 04 09:20:48 localhost dbus-daemon\[2859\]: \[session uid=1000 pid=2859 pidfd=5\] Successfully activated service 'org.gnome.keyring.SystemPrompter'
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: bus acquired: org.gnome.keyring.PrivatePrompter
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: acquired name: org.gnome.keyring.SystemPrompter
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: creating new GcrPromptDialog prompt
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: automatically selecting secret exchange protocol
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: generating public key
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: beginning the secret exchange: \[sx-aes-1\]\\npublic=ZYcCsitgmWeIbN2TD3lIEsbEUUEIh4/CQLg4yMZAlLdRMFtTFGOKEFUGdYszVeTl5G669rEpGBhZPrBIetPTNBmeO90ZzgFbrUjcTgu5pejO>
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: acquired name: org.gnome.keyring.PrivatePrompter
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: receiving secret exchange: \[sx-aes-1\]\\npublic=3i90mNDBEvI85Be4ZuJe2QS7n2EHH9sVpT/PbcYobxn2KdxVgI9mALro3mmrVfjEcmcztyd2cFdL8CMNuCK/krqfA+PBdrp3psO71lJ/XNcYP9mA>
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: deriving shared transport key
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: deriving transport key
Sep 04 09:20:48 localhost gcr-prompter\[4280\]: Gcr: starting password prompt for callback /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: completed password prompt for callback :1.53@/org/gnome/keyring/Prompt/p2
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: sending the secret exchange: \[sx-aes-1\]\\npublic=ZYcCsitgmWeIbN2TD3lIEsbEUUEIh4/CQLg4yMZAlLdRMFtTFGOKEFUGdYszVeTl5G669rEpGBhZPrBIetPTNBmeO90ZzgFbrUjcTgu5pejOFq>
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: closing the prompt
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p2@:1.53
Sep 04 09:21:32 localhost gcr-prompter\[4280\]: Gcr: calling the PromptDone method on /org/gnome/keyring/Prompt/p2@:1.53, and ignoring reply
Sep 04 09:21:42 localhost gcr-prompter\[4280\]: Gcr: 10 second inactivity timeout, quitting
Sep 04 09:21:42 localhost gcr-prompter\[4280\]: Gcr: unregistering prompter
Sep 04 09:21:42 localhost gcr-prompter\[4280\]: Gcr: disposing prompter
Sep 04 09:21:42 localhost gcr-prompter\[4280\]: Gcr: finalizing prompter
Sep 04 09:22:42 localhost updatecheck-daemon\[3302\]: /usr/libexec/systemcheck/updatecheck-daemon: INFO: loop start.

Might be triggered by a hardening setting. Some of our configuration causes specific hardware to malfunction but not others.

Reboot the system, but on the boot menu, press the e key to edit boot settings, Move your cursor to the line that starts with linux, then remove gather_data_sampling=force from the command line. Then press Ctrl+X to boot. If KeePassXC works then, reboot into sysmaint mode, then use the following instructions to remove gather_data_sampling=force permanently:

Some documentation about gather_data_sampling=force sometimes causing issues:

illegal hardware instruction is SIGILL, so the binary is hitting an opcode your cpu doesnt have. that matches it working in the vms (they usually advertise a newer cpu) and dying on bare metal. check lscpu for avx/avx2 flags, then try an older keepassxc build or a flatpak aimed at a lower baseline. appimage dying the same way points at the binary, not kicksecure packaging.

@nite_route SIGILL usually, but not always, points to a binary hitting an opcode the CPU doesn’t have. In this instance, it’s known that one of the hardening measures Kicksecure enables can result in spurious SIGILLs from programs that are CPU-compatible, as covered above.