You are not logged in.
After updating something, keepassxc, which I've been using daily for years now fails (v2.7.9-4):
$ keepassxc
Illegal instruction (core dumped)
...
$ coredumpctl info 79170
PID: 79170 (keepassxc)
UID: 1000 (jo)
GID: 1000 (jo)
Signal: 4 (ILL)
Timestamp: Sat 2024-10-26 17:26:50 CEST (18s ago)
Command Line: keepassxc
Executable: /usr/bin/keepassxc
Control Group: /user.slice/user-1000.slice/user@1000.service/tmux-spawn-3465c2ac-3b35-4781-9132-612a7b7c9e22.scope
Unit: user@1000.service
User Unit: tmux-spawn-3465c2ac-3b35-4781-9132-612a7b7c9e22.scope
Slice: user-1000.slice
Owner UID: 1000 (jo)
Boot ID: 8cc775d9e32844f0b19dfc5c1f941c72
Machine ID: 4f0640d32193461ba64fc4d11f4a0c4f
Hostname: sbMb
Storage: /var/lib/systemd/coredump/core.keepassxc.1000.8cc775d9e32844f0b19dfc5c1f941c72.79170.1729956410000000.zst (present)
Size on Disk: 1M
Message: Process 79170 (keepassxc) of user 1000 dumped core.
Stack trace of thread 79170:
#0 0x000078528bdea869 n/a (libbotan-3.so.6 + 0x1ea869)
#1 0x000078528bdf42c1 n/a (libbotan-3.so.6 + 0x1f42c1)
#2 0x00005d37608e3b07 n/a (keepassxc + 0xdbb07)
#3 0x00005d37608e3bfa n/a (keepassxc + 0xdbbfa)
#4 0x00005d37608e5e19 n/a (keepassxc + 0xdde19)
#5 0x00005d37608d3a3d n/a (keepassxc + 0xcba3d)
#6 0x000078528a830e08 n/a (libc.so.6 + 0x25e08)
#7 0x000078528a830ecc __libc_start_main (libc.so.6 + 0x25ecc)
#8 0x00005d37608dc395 _start (keepassxc + 0xd4395)
Stack trace of thread 79172:
#0 0x000078528a91663d __poll (libc.so.6 + 0x10b63d)
#1 0x000078528a73020b n/a (libxcb.so.1 + 0xd20b)
#2 0x000078528a731f3d xcb_wait_for_event (libxcb.so.1 + 0xef3d)
#3 0x0000785286929599 n/a (libQt5XcbQpa.so.5 + 0x5e599)
#4 0x000078528aef295b n/a (libQt5Core.so.5 + 0xf295b)
#5 0x000078528a89f39d n/a (libc.so.6 + 0x9439d)
#6 0x000078528a92449c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 79171:
#0 0x000078528a916bb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x0000785289693227 n/a (libglib-2.0.so.0 + 0xc0227)
#2 0x000078528962fa55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
#3 0x000078528b0fe1af _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f>
#4 0x000078528b0a6b9c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a6b9c)
#5 0x000078528aef2abd _ZN7QThread4execEv (libQt5Core.so.5 + 0xf2abd)
#6 0x000078528cae2bf3 n/a (libQt5DBus.so.5 + 0x17bf3)
#7 0x000078528aef295b n/a (libQt5Core.so.5 + 0xf295b)
#8 0x000078528a89f39d n/a (libc.so.6 + 0x9439d)
#9 0x000078528a92449c n/a (libc.so.6 + 0x11949c)
ELF object binary architecture: AMD x86-64So I tried reinstalling some packages: sudo pacman -S botan glib2 glibc qt5-base, with some reboots, no improvement.
So I switched to keepassxc-git: makepkg took a long, long time, then
$ keepassxc
Illegal instruction (core dumped)
...
$ coredumpctl info 74127
PID: 74127 (keepassxc)
UID: 1000 (jo)
GID: 1000 (jo)
Signal: 4 (ILL)
Timestamp: Sat 2024-10-26 16:29:34 CEST (49min ago)
Command Line: keepassxc
Executable: /usr/bin/keepassxc
Control Group: /user.slice/user-1000.slice/user@1000.service/tmux-spawn-3465c2ac-3b35-4781-9132-612a7b7c9e22.scope
Unit: user@1000.service
User Unit: tmux-spawn-3465c2ac-3b35-4781-9132-612a7b7c9e22.scope
Slice: user-1000.slice
Owner UID: 1000 (jo)
Boot ID: 8cc775d9e32844f0b19dfc5c1f941c72
Machine ID: 4f0640d32193461ba64fc4d11f4a0c4f
Hostname: sbMb
Storage: /var/lib/systemd/coredump/core.keepassxc.1000.8cc775d9e32844f0b19dfc5c1f941c72.74127.1729952974000000.zst (present)
Size on Disk: 1M
Message: Process 74127 (keepassxc) of user 1000 dumped core.
Stack trace of thread 74127:
#0 0x000072b98edea869 n/a (libbotan-3.so.6 + 0x1ea869)
#1 0x000072b98edf42c1 n/a (libbotan-3.so.6 + 0x1f42c1)
#2 0x0000602eddd2c729 _ZN5Botan20Buffered_Computation5finalISt6vectorIhNS_16secure_allocatorIhEEEEET_v (keepassxc + 0x263729)
#3 0x0000602eddd2c85a _ZN10CryptoHash4hashERK10QByteArrayNS_9AlgorithmE (keepassxc + 0x26385a)
#4 0x0000602eddb949f2 testSha256 (keepassxc + 0xcb9f2)
#5 0x000072b98ce30e08 n/a (libc.so.6 + 0x25e08)
#6 0x000072b98ce30ecc __libc_start_main (libc.so.6 + 0x25ecc)
#7 0x0000602eddba4e65 _start (keepassxc + 0xdbe65)
Stack trace of thread 74128:
#0 0x000072b98cf16bb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x000072b98bdfb227 n/a (libglib-2.0.so.0 + 0xc0227)
#2 0x000072b98bd97a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
#3 0x000072b98d6fe1af _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f>
#4 0x000072b98d6a6b9c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a6b9c)
#5 0x000072b98d4f2abd _ZN7QThread4execEv (libQt5Core.so.5 + 0xf2abd)
#6 0x000072b98f3c2bf3 n/a (libQt5DBus.so.5 + 0x17bf3)
#7 0x000072b98d4f295b n/a (libQt5Core.so.5 + 0xf295b)
#8 0x000072b98ce9f39d n/a (libc.so.6 + 0x9439d)
#9 0x000072b98cf2449c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 74129:
#0 0x000072b98cf1663d __poll (libc.so.6 + 0x10b63d)
#1 0x000072b98d95020b n/a (libxcb.so.1 + 0xd20b)
#2 0x000072b98d951f3d xcb_wait_for_event (libxcb.so.1 + 0xef3d)
#3 0x000072b989129599 n/a (libQt5XcbQpa.so.5 + 0x5e599)
#4 0x000072b98d4f295b n/a (libQt5Core.so.5 + 0xf295b)
#5 0x000072b98ce9f39d n/a (libc.so.6 + 0x9439d)
#6 0x000072b98cf2449c n/a (libc.so.6 + 0x11949c)
ELF object binary architecture: AMD x86-64Finally, flatpak install --user flathub org.keepassxc.KeePassXC got me a working KeePassXC (v2.7.9). But wtf - any ideas what went wrong with the Arch packages?
Offline
fyi keepassxc 2.7.9-4 works without problem on my machine.
Offline
With what CPU? It looks like botan is requiring things your CPU doesn't have. What version of botan do you have now, and what version did you have previously that worked?
Last edited by Scimmia (2024-10-26 23:16:00)
Offline
AMD FX(tm)-8350 Eight-Core Processor. From my logs I see that 24/10 I upgraded botan 3.5.0-1 -> 3.6.0-1, apparently provoking this bug. Since I've switched to the flatpak, botan got uninstalled.
Offline
botan 3.6.1 is probably fixed and would work on your machine.
https://botan.randombit.net/news.html
Fix a bug in x86 CPUID detection introduced in 3.6.0 which would cause crashes on systems which have BMI1 but not BMI2. (GH #4402 #4401)
Last edited by progandy (2024-10-28 22:23:45)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
That is indeed one of the processors with BMI1 but not BMI2, mystery solved.
Offline
Updates done, including to botan 3.6.1-1 and keepassxc is working again, thanks!
Offline