Bug 392285 - AppImage fails on PCLINUXOS because the distributions sets QT_PLUGIN_PATH
Summary: AppImage fails on PCLINUXOS because the distributions sets QT_PLUGIN_PATH
Status: RESOLVED DOWNSTREAM
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: 4.0
Platform: PCLinuxOS Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-24 20:33 UTC by ozviewer
Modified: 2018-03-27 08:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
System information (84.99 KB, image/png)
2018-03-24 21:17 UTC, ozviewer
Details
PCLOS version.png (84.99 KB, image/png)
2018-03-24 21:24 UTC, ozviewer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ozviewer 2018-03-24 20:33:22 UTC
Trying to run Krita 4.0 appimage, the installation fails when the appimage accesses some shared object files. For example, when first run the following error message appears and the appimage load process stops:

"/usr/lib64/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so: undefined symbol: _ZN13KWindowSystem17isPlatformWaylandEv"

If I delete the .so file and run the appimage again, another .so file with a similar message is found and the appimage stops. If I again delete the .so file and start again, another .so file is found. This happened 5 or 6 times and each time I deleted the specified .so file. Then the appimage loaded and Krita 4.0 ran without a problem. However, my KDE system was not running as it should because it needed at least some of the .so files. I had to restore my system from a backup.
Comment 1 Halla Rempt 2018-03-24 21:04:41 UTC
Did you also report this on Reddit? In any case, given that this is, of course, not something that happens to everyone who uses the appimage, more information is needed about your system. Which version of "pclinuxos" are you running?
Comment 2 ozviewer 2018-03-24 21:17:43 UTC
Created attachment 111619 [details]
System information
Comment 3 ozviewer 2018-03-24 21:24:23 UTC
Created attachment 111620 [details]
PCLOS version.png

Hi Boudewijn,

I have uploaded a png of my system details (attached) to the bug
tracker. I am happy to help with any further information or testing.

Regards,
Oz


On 25/03/18 08:04, Boudewijn Rempt wrote:
> https://bugs.kde.org/show_bug.cgi?id=392285
>
> Boudewijn Rempt <boud@valdyas.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|UNCONFIRMED                 |NEEDSINFO
>           Resolution|---                         |WAITINGFORINFO
>                   CC|                            |boud@valdyas.org
>
> --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> ---
> Did you also report this on Reddit? In any case, given that this is, of course,
> not something that happens to everyone who uses the appimage, more information
> is needed about your system. Which version of "pclinuxos" are you running?
>
Comment 4 ozviewer 2018-03-24 21:29:34 UTC
Comment on attachment 111620 [details]
PCLOS version.png

Duplicate
Comment 5 ozviewer 2018-03-24 22:11:02 UTC
I forgot to add that the Krita 3.3 appimage works fine.
Comment 6 Halla Rempt 2018-03-26 11:42:21 UTC
The 3.3.3 appimage is made with a different and tool and a different version of Qt, so that's not so strange.
Comment 7 Halla Rempt 2018-03-26 11:46:10 UTC
.
Comment 8 ozviewer 2018-03-26 21:17:33 UTC
As I need Krita 4.0, and I appear to be the only one with this problem, I have overcome it by changing my distro to Manjaro. The Krita 4.0 appimage runs without issue. Unfortunately this means I can't do any further tests of the bug on PCLinuxOS as I don't have it.
Comment 9 Halla Rempt 2018-03-27 08:08:01 UTC
Okay, I have been able to test with pclinuxos in a vm. The problem seems to be that the distribution is setup with a hard-coded QT_PLUGIN_PATH=/usr/lib64/qt5. 

As noted in https://doc.qt.io/qt-5.10/deployment-plugins.html, "Note: QT_PLUGIN_PATH should not be exported as a system-wide environment variable since it can interfere with other Qt installations."

But because it is set, the Qt inside the appimage also looks in that location, tries to load the plugins and fails because it has different Qt versions. The solution would be to unset QT_PLUGIN_PATH before starting Krita. I'll see how hard the pclinuxos guys make reporting issues.