| Summary: | Qt applications using a different Qt than system one are broken, remove QT_PLUGIN_PATH from system-wide environment variables | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Timothée Giet <animtim> |
| Component: | RPM Packages | Assignee: | David GEIGER <geiger.david68210> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | release_blocker | CC: | alejandro.anv, fri, mageia, unruh, yvesbrungard |
| Version: | Cauldron | ||
| Target Milestone: | Mageia 8 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7TOO | ||
| Source RPM: | qtbase5-5.12.6-1.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Timothée Giet
2019-07-03 20:34:52 CEST
@Timothée Thank you for your researched, thorough & helpful report. Assigning initially to neoclust as the Qt maintainer. CC:
(none) =>
lewyssmith Problem stills there. From https://doc.qt.io/qt-5/deployment-plugins.html **Note: Do not export QT_PLUGIN_PATH as a system-wide environment variable because it can interfere with other Qt installations.** CC:
(none) =>
alejandro.anv https://bugs.mageia.org/show_bug.cgi?id=26112#c0 duplicates this complaint - the comment above: Alejandro Vargas 2020-01-21 09:38:14 CET In files /etc/profile.d/60qt5.csh and /etc/profile.d/60qt5.sh please remove QT_PLUGIN_PATH This is a bug that prevents programs using different version of QT to run (like appimages). See https://doc.qt.io/qt-5/deployment-plugins.html that says: Note: Do not export QT_PLUGIN_PATH as a system-wide environment variable because it can interfere with other Qt installations. ---------- Both files come from pkg qtbase5-common, in qtbase5-5.12.6-1.mga7.src.rpm This problem clearly matters, and appears easy to fix. Assigning to DavidG as the active maintainer; CC'ing Nicolas for his view. Source RPM:
qtbase5-5.12.2-2.mga7.src.rpm =>
qtbase5-5.12.6-1.mga7.src.rpm *** Bug 26112 has been marked as a duplicate of this bug. *** I ran into this with RPCS3 too: https://github.com/RPCS3/rpcs3/issues/6986 While debugging we came to the same conclusions, and a bug report was filed upstream with AppImage: https://github.com/probonopd/linuxdeployqt/issues/416 I think it could possibly be mitigated in AppImage (e.g. by forcefully unsetting QT_PLUGIN_PATH), but we seem to be the odd ones out with this environment variable so we should review whether we really need it. As Alejandro pointed out, the Qt 5 docs explicitly say that this should not be done. Hello, Same problem with Zoom which seems to be an AppImage. The variable QT_PLUGIN_PATH is defined in the spec file: http://svnweb.mageia.org/packages/cauldron/qtbase5/current/SPECS/qtbase5.spec?view=markup#l1833 Could this part be deleted ? # Set the QT_PLUGIN_PATH environment variable if [ -z \$(echo \$QT_PLUGIN_PATH | grep "kcms") ]; then QT_PLUGIN_PATH="%{_qt5_plugindir}:%{_qt5_plugindir}/kcms:\$QT_PLUGIN_PATH" export QT_PLUGIN_PATH fi see also bug 18209 bug 17891 bug 16765 CC:
(none) =>
yves.brungard_mageia This definitely is a problem with Zoom, the conferencing program, and the most recent (5.4.xx) versions. zoom crashes with a segfault when it starts. Using (unset QT_PLUGIN_PATH; zoom ) fixes the problem. So, QT_PLUGIN_PATH should not be set in the first place. This is in Mageia 7.1 (and it is 4 months since this was first reported). Because Zoom is so crucial to both remote work and sanity during this time of Covid, breaking people's lifeline is not a good idea. CC:
(none) =>
unruh
Rémi Verschelde
2020-12-27 21:49:24 CET
Severity:
normal =>
critical Increasing to release blocker as discussed with neoclust. Priority:
High =>
release_blocker So in Cauldron too. Target Milestone:
--- =>
Mageia 8 we removed the QT_PLUGIN_PATH some weeks ago. What is the status of this bug ? In mga7, the bug is still there (I guess QT_PLUGIN_PATH has been removed only on cauldron). I can't test it on cauldron as I don't have it installed now, but you can check easily: download Krita appimage (https://download.kde.org/stable/krita/4.4.1/krita-4.4.1-x86_64.appimage), set it executable and try to launch it. If it starts properly, the bug is fixed. If it stops/crashes while starting, the bug is not fixed. Hello, In my cauldron up to date. env|grep QT_ QT_XFT=0 QT_AUTO_SCREEN_SCALE_FACTOR=0 Thus QT_PLUGIN_PATH is no more set, what is wanted. krita downloaded as said by Animtim stars OK. Thus, the bug can be closed. If side effects occur, other reports have to be filed. Status:
NEW =>
RESOLVED |