https://bugs.kde.org/show_bug.cgi?id=500035
--- Comment #3 from a....@inwind.it --- (In reply to Nicolas Fella from comment #2) > Somehow your system seems to be in an inconsistent update state. Make sure > to fully update and reboot Hi! Before giving up and submitting this bug I "dnf update"d, kexeced and rebooted multiple times. All clear on dnf side. However, your suggestion helped, because I had to reframe the problem. A "locate 6.8.1" showed that there were some Qt 6.8.1 files, not belonging to any package, alongside the correct version (6.8.2). Their name had a strange suffix ";6782cced" appended. Looking for that suffix, I've found more than a hundred files of this form (shortened list): ``` /usr/lib/.build-id/07/c2b56d25bb889215dc7ca7fa4c3961c2235006;6782cced /usr/lib/.build-id/15/fa55a1a7c7fd31a617b8b168dc80e00a1e11f9;6782cced [...] /usr/lib64/libQt6Concurrent.so.6.8.1;6782cced /usr/lib64/libQt6Concurrent.so.6;6782cced /usr/lib64/libQt6Core.so.6.8.1;6782cced /usr/lib64/libQt6Core.so.6;6782cced /usr/lib64/libQt6DBus.so.6.8.1;6782cced /usr/lib64/libQt6DBus.so.6;6782cced /usr/lib64/libQt6Network.so.6.8.1;6782cced /usr/lib64/libQt6Network.so.6;6782cced /usr/lib64/libQt6Sql.so.6;6782cced /usr/lib64/libQt6Test.so.6.8.1;6782cced /usr/lib64/libQt6Test.so.6;6782cced /usr/lib64/libQt6Xml.so.6.8.1;6782cced /usr/lib64/libQt6Xml.so.6;6782cced /usr/lib64/qt6/plugins/networkinformation/libqglib.so;6782cced /usr/lib64/qt6/plugins/networkinformation/libqnetworkmanager.so;6782cced /usr/lib64/qt6/plugins/sqldrivers/libqsqlite.so;6782cced /usr/lib64/qt6/plugins/tls/libqcertonlybackend.so;6782cced /usr/lib64/qt6/plugins/tls/libqopensslbackend.so;6782cced /usr/lib64/qt6/sbom/qtbase-6.8.1.spdx;6782cced [...] ``` I guess the mistery now is what did this rename. I am willing to think that is some internal operational detail of how rpm updates a package. The other unsettling discovery was that ld-linux decided to load /usr/lib64/libQt6Sql.so.6;6782cced (there were no symlinks pointing to it: it just hat that weird name). Shouldn't there be some sort of protection there? Could I simply drop a gadget in /usr/lib64 and it gets loaded without a fuss? Anyway, this problem is related to my distribution (Fedora) and not to the KDE upstream project. Thanks for your support! -- You are receiving this mail because: You are watching all bug changes.
