Qt6 crash: undefined symbol: version Qt_6_PRIVATE_API
Is this a new report?
Yes
System Info
Void 6.1.94_1 x86_64 AuthenticAMD uptodate FFFFFF
Package(s) Affected
qt6-*-6.6.0_1,qt6-*-6.7.2_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
Qt applications such as K3b or PCManFM-Qt should start without any error.
Actual behaviour
Qt applications launched from a window manager do not run, and running them from a terminal gives an error such as pcmanfm-qt: symbol lookup error: /usr/lib/libQt6WaylandClient.so.6: undefined symbol: _ZTIN16QNativeInterface7Private14QWaylandScreenE, version Qt_6_PRIVATE_API
It could potentially be linked to several of the qt6 package updates but for now this is what I get.
Steps to reproduce
- Update qt6
- Launch a Qt application
It seems to be more than just qt6-wayland. qt6-wayland, qt6-svg, qt6-webchannel, and qt6-websockets were updated to 6.7.2_1, and this is the error now:
pcmanfm-qt: symbol lookup error: /usr/lib/libLayerShellQtInterface.so.6: undefined symbol: _ZN15QtWaylandClient14QWaylandWindow12handleExposeERK7QRegion, version Qt_6_PRIVATE_API
ImportError: /usr/lib/python3.12/site-packages/PyQt6/QtCore.abi3.so: undefined symbol: _ZN14QReadWriteLock16destroyRecursiveEP21QReadWriteLockPrivate, version Qt_6_PRIVATE_API
all matching cases online suggest towards rebuilding all qt6 apps against upstream qt6
currently in progress: https://build.voidlinux.org/waterfall
Plasma 6 also fails to start due to the Qt6 update
plasmashell: symbol lookup error: /usr/lib/libLayerShellQtInterface.so.6: undefined symbol: _ZN15QtWaylandClient14QWaylandWindow12handleExposeERK7QRegion, version Qt_6_PRIVATE_API
PrismLauncher and Kdenlive don't work
With the latest updates i can't connect into plasma 6 using sddm, it loops back to sddm after entering the password...
qtcreator fails because of this :-/
With the latest updates i can't connect into plasma 6 using sddm, it loops back to sddm after entering the password...
Don't know why all comments including this one are saying resolved. Particularly this one. This is still a prominent issue.
With the latest updates i can't connect into plasma 6 using sddm, it loops back to sddm after entering the password...
Don't know why all comments including this one are saying resolved. Particularly this one. This is still a prominent issue.
They're queued to be rebuilt. I need to hide them to keep track of which one was processed.
Dunno if it's necessary to individually mention apps, but rssguard is also affected.
telegram-desktop affected too, telegram-desktop: symbol lookup error: telegram-desktop: undefined symbol: _ZN14QReadWriteLock16destroyRecursiveEP21QReadWriteLockPrivate, version Qt_6_PRIVATE_API
PCManFM-Qt and other applications now work with the latest packages that have finished building. Will close.
I have the same issue with dooble.
Is this resolved ?
Is this resolved ?
Unless you're going to test all packages that requires Qt6, or rebuild all of them, no!
- [x]
partitionmanageris also affected
Does this also occur in v24.08.03 ?
The issue has reappeared today with corectrl
Given the following update:
qt6-core update 6.8.2_5 6.10.0_1 -
qt6-dbus update 6.8.2_5 6.10.0_1 -
qt6-gui update 6.8.2_5 6.10.0_1 -
qt6-network update 6.8.2_5 6.10.0_1 -
qt6-opengl-widgets update 6.8.2_5 6.10.0_1 -
qt6-sql update 6.8.2_5 6.10.0_1 -
qt6-widgets update 6.8.2_5 6.10.0_1 -
corectrl produces the following output when run from a terminal:
corectrl: symbol lookup error: /usr/lib/libQt6Qml.so.6: undefined symbol: _ZN14QObjectPrivateC2Ei, version Qt_6_PRIVATE_API
Fix is downgrading as follows:
sudo xdowngrade /var/cache/xbps/qt6-core-6.8.2_5.x86_64.xbps /var/cache/xbps/qt6-dbus-6.8.2_5.x86_64.xbps /var/cache/xbps/qt6-gui-6.8.2_5.x86_64.xbps /var/cache/xbps/qt6-network-6.8.2_5.x86_64.xbps /var/cache/xbps/qt6-opengl-widgets-6.8.2_5.x86_64.xbps /var/cache/xbps/qt6-sql-6.8.2_5.x86_64.xbps /var/cache/xbps/qt6-widgets-6.8.2_5.x86_64.xbps
Given how commits into void-packages as of writing this seem to have ceased two hours ago with no further rebuilds being listed, I can't pinpoint this to a partial upgrade due to server compile latency
There are also packages like qt6-svg-6.8.2_1 seemingly still stuck on version 6.8 with no updates to 6.10 in sight. Missing rebuilds?
May be related to this: https://github.com/void-linux/void-packages/issues/57727
EDIT: Fixed an error on xdowngrade line and clarified some things
EDIT Again: Reading https://github.com/void-linux/void-packages/commit/a7de2992fa82ad9dc12bbba241a5abe6b31e64e2 it appears packages like qt6-svg-6.8.2_1 do indeed have a scheduled update to 6.10, although this doesn't appear to have dropped still. Buildbot x86_64 at https://build.voidlinux.org/#/builders/7/builds/3928 reports to be busy building a version of Chromium right now.
In the meantime, libqt6shadertools-6.10.0_1 has appeared in my update list, was absent before.
Hopefully it's just the buildbot being overwhelmed
I was dropped to a tty and KDE didn't even start after updating the system.
In addition to packages listed in @TeusLollo reply, I had to downgrade following to get my KDE system up again:
qt6-core, qt6-dbus, qt6-gui, qt6-network, qt6-opengl-widget, qt6-sql, qt6-svg, qt6-widget, qt6-concurrent, qt6-plugin-sqlite, qt6-plugin-tls-openssl, qt6-plugin-tls-qcertonly, qt6-xml, qt6-plugin-networkinformation, qt6-printsupport
Downgraded all of them from 6.10.0_1, back to 6.8.2_5.
I don't know if this is due to server updates not yet delivered / synced but this resolved the problem for me.
Been having similar issues, LXQT and SDDM don't even start. Gonna try to downgrade the packages and see if that fixes anything.
Qt6 build not finished. Wait for 3 more days, plz.
Move to #57727