Summary: | crash at initial KDE startup | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | a.mux |
Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | a.mux, nicolas.fella |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/132724/events/5d581d3ecb50483db38b802fcc5fc0e9/ |
Description
a.mux
2025-02-13 22:28:23 UTC
Looking in the backtrace via coredumpctl and in the journal, I also saw this message: Cannot mix incompatible Qt library (6.8.1) with this library (6.8.2) This is a bit unsettling, because I have no package containing 6.8.1 in my system: $ sudo rpm -qa | rg --fixed-strings "6.8.1" [EMPTY LIST] And all my qt libraries are at 6.8.2: sudo rpm -qa | rg --fixed-strings "6.8.2" mercurial-6.8.2-1.fc41.x86_64 qt6-filesystem-6.8.2-1.fc41.x86_64 qt6-qtbase-common-6.8.2-2.fc41.noarch qt6-qtbase-6.8.2-2.fc41.x86_64 qt6-qtserialport-6.8.2-1.fc41.x86_64 qt6-qtwebsockets-6.8.2-1.fc41.x86_64 qt6-qtbase-mysql-6.8.2-2.fc41.x86_64 qt6-qtconnectivity-6.8.2-1.fc41.x86_64 qt6-qttools-common-6.8.2-1.fc41.noarch qt6-qtbase-gui-6.8.2-2.fc41.x86_64 qt6-qtsvg-6.8.2-1.fc41.x86_64 qt6-qtdeclarative-6.8.2-1.fc41.x86_64 qt6-qtwayland-6.8.2-1.fc41.x86_64 qt6-qtvirtualkeyboard-6.8.2-1.fc41.x86_64 qt6-qttools-6.8.2-1.fc41.x86_64 qt6-qtpositioning-6.8.2-1.fc41.x86_64 qt6-qtsensors-6.8.2-1.fc41.x86_64 qt6-qtshadertools-6.8.2-1.fc41.x86_64 qt6-qt5compat-6.8.2-1.fc41.x86_64 qt6-qtquicktimeline-6.8.2-1.fc41.x86_64 qt6-qtquick3d-6.8.2-1.fc41.x86_64 qt6-qtmultimedia-6.8.2-1.fc41.x86_64 qt6-qtspeech-6.8.2-1.fc41.x86_64 qt6-qtpdf-6.8.2-1.fc41.x86_64 qt6-qtwebchannel-6.8.2-1.fc41.x86_64 qt6-qtwebengine-6.8.2-1.fc41.x86_64 qt6-qtwebview-6.8.2-1.fc41.x86_64 qt6-qtspeech-speechd-6.8.2-1.fc41.x86_64 qt6-qtimageformats-6.8.2-1.fc41.x86_64 qt6-qttranslations-6.8.2-1.fc41.noarch Somehow your system seems to be in an inconsistent update state. Make sure to fully update and reboot (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! |