I installed kicksecure-cli on my Debian 12 machine and it breaks latest Firefox-ESR and KeepassXC.
On Firefox, some sites cause crash. Error message: [Parent 1234, IPC I/O Parent] WARNING: process 53223 exit on signal 4: file ./ipc/chromium/src/base/process_util_posix.cc:264
KeepassXC error message: illegal instructions (core dump)
Both fixed after purging all Kicksecure packages and reinstall dbus.
On hardware, i.e. not a VM?
Firefox from packages.debian.org? Simple…
firefox
Or flatpak or something?
Do you know a website where this is reliably reproducible?
I cannot reproduce this anywhere.
Sorry for late reply.
Yes it is running on hardware and not a VM.
It is latest firefox-esr from Debian stable repo.
Hello,
thank you for the existence of this project.
I have the same issue with KeepassXC since some Kicksecure updates in 2 Kicksecure VMs running on 2 different hypervisors. On one hypervisor this issue also occurs.
The following package combination is not affected:
sudo dpkg -l | grep kicksecure
ii apparmor-profiles-kicksecure 3:28.8-1
ii kicksecure-base-files 3:7.5-1
ii kicksecure-cli 3:28.8-1
ii kicksecure-cli-vm 3:28.8-1
ii kicksecure-default-applications-cli 3:28.8-1
ii kicksecure-dependencies-cli 3:28.8-1
ii kicksecure-dependencies-system 3:28.8-1
ii kicksecure-desktop-applications-recommended 3:28.8-1
ii kicksecure-desktop-applications-xfce 3:28.8-1
ii kicksecure-desktop-environment-essential-gui 3:28.8-1
ii kicksecure-desktop-environment-essential-xfce 3:28.8-1
ii kicksecure-network-conf 3:6.3-1
ii kicksecure-network-conf-gui 3:6.3-1
ii kicksecure-recommended-cli 3:28.8-1
ii kicksecure-welcome-page 3:6.5-1
ii kicksecure-xfce 3:28.8-1
ii kicksecure-xfce-vm 3:28.8-1
An update to any newer version means that KeepassXC can no longer be used:
illegal instructions (core dump) is the error message. In addition, the counter for incorrect password entries in the terminal no longer works, it displays “-2”.
Backups have been restored. The Kicksecure repo was commented out in the sources.lists to prevent the defective versions from being received.
Can you help with this? KeepassXC is needed every day.
Best regards
PrivacyTux
No, because I cannot reproduce this.
Try reporting a bug against KeepassXC and please share the link to the report here.
Wild guess: Kernel Issues
It is possible to reproduce the problem when booting a current Debian 5.10 or a non Debian 5.15 kernel. With a 6.1 kernel, the problem does not exist if you use current Kicksecure packages. In mid-2024 the Kicksecure packages were compatible with the 5.10 kernel of Debian Bullseye in Debian Bookworm.
Can you please try again to reproduce the problem with a current 5.10 kernel, e.g. from the Debian Bullseye repository?