Keepassxc won't start on arch based linux

[akyag]

KeepassXC won't start since yesterday. Here's what I am getting in terminal

akya@quady ~> keepassxc
fish: Job 1, 'keepassxc' terminated by signal SIGILL (Illegal instruction)

journalctl

akya@quady ~ [SIGILL]> journalctl -b 0 | grep keepassxc
Oct 23 18:27:04 quady kernel: traps: keepassxc[2067] trap invalid opcode ip:7de5583ea869 sp:7ffceaf733c0 error:0 in libbotan-3.so.6.6.0[7de5582c5000+3fe000]
Oct 23 18:27:04 quady systemd[1420]: app-org.keepassxc.KeePassXC@autostart.service: Main process exited, code=killed, status=4/ILL
Oct 23 18:27:04 quady systemd[1420]: app-org.keepassxc.KeePassXC@autostart.service: Failed with result 'signal'.
Oct 23 18:27:11 quady cryptomator[2768]: 18:27:11.243 [JavaFX Application Thread] ERROR org.keepassxc.LinuxMacConnection - Cannot connect to proxy. Is KeepassXC started?
Oct 23 18:28:28 quady kernel: traps: keepassxc[5257] trap invalid opcode ip:773f62fea869 sp:7fff0165d540 error:0 in libbotan-3.so.6.6.0[773f62ec5000+3fe000]
Oct 23 18:54:16 quady kernel: traps: keepassxc[61218] trap invalid opcode ip:749228bea869 sp:7ffe8e3ae9d0 error:0 in libbotan-3.so.6.6.0[749228ac5000+3fe000]
Oct 23 18:54:24 quady kernel: traps: keepassxc[61550] trap invalid opcode ip:7578f6dea869 sp:7ffc376375e0 error:0 in libbotan-3.so.6.6.0[7578f6cc5000+3fe000]

Version info

akya@quady ~> keepassxc --debug-info 
KeePassXC - Version 2.7.9
Revision: 8f6dd13

Qt 5.15.15
Debugging mode is disabled.

Operating system: EndeavourOS
CPU architecture: x86_64
Kernel: linux 6.6.57-1-lts

Enabled extensions:
- Auto-Type
- Browser Integration
- Passkeys
- SSH Agent
- KeeShare
- YubiKey
- Secret Service Integration

Cryptographic libraries:
- Botan 3.6.0

Operating System: Linux Endeavour OS Desktop Env: KDE Windowing System: Wayland

---

Edit: is this same as https://github.com/keepassxreboot/keepassxc/issues/11385

[droidmonkey]

Possibly the same, it's crashing in botan3. This isn't a problem with our program, please file a bug with arch.

[SmallAndSoft]

I am having the same issue. I have a suspicion that it is due to CPU not having AVX2.