Could it be libQt6Core? dmesg -T is full of drkonqi-coredum[17665]: segfault at 0 ip 00007f4db46345c3 sp 00007ffe25cce738 error 4 in libQt6Core.so.6.11.1[2345c3,7f4db44c2000+457000]
It probably isn't libQt6Core, after a reboot crashes keep happening but libQt6Core errors aren't present in dmesg yet
The segfault inside libQt6Core.so.6.11.1 is a useful clue — a null pointer dereference in Qt6Core would explain crashes across all Qt-based applications (plasma, kwallet, kate, bluetooth stack). Since others are not reporting this, the issue is most likely specific to your installation.
A few things worth checking:
Verify the integrity of the Qt6Core package (detects file corruption or partial upgrades):
rpm -V libQt6Core
Check that all Qt6 packages are on the same version:
rpm -qa | grep -E "^libQt6|^qt6" | sort
If any package is on a different version, a full upgrade or selective reinstall may fix it:
sudo dnf reinstall libQt6Core
The "abysmal performance" combined with widespread crashes could also point to a hardware memory issue. If the above checks come back clean, it would be worth running a memtest pass.
Hi thank you for the reply. I also discovered this one
$ LD_PRELOAD=/usr/lib64/libthread_db.so.1 kate -n
kate: symbol lookup error: /usr/lib64/libthread_db.so.1: undefined symbol: ps_pdwrite
rpm -V libQt6Core returned nothing. rpm -qa | grep -E "^libQt6|^qt6" | sort showed all 6.11.1-1mamba
sudo dnf reinstall libQt6Core and rebooting didn't change the situation
I can get kate to crash consistently when any scrolling (horizontal/vertical) happens, I am testing with that
I could let memtest run overnight but I am more suspicious of some library over the hardware being faulty
The reason I suspect some shared library is that non-openmamba software (edge, vscode...) are not crashing despite having bad performance. These come with a bunch of statically linked libraries.
Another solid test would be to have an older version of openmamba at hand to install, but I don't have that. I do have windows installed too, and that one is working fine (fine by microsoft standards).
