Discussion:
[mitk-users] Linux package contains Qt libraries but no plugins
Sascha Zelzer
2017-07-17 16:40:08 UTC
Permalink
Hi,

I just tried the MITK 2016.11 Linux binary (I have a MR dicom series to
view) and got the (kind of) common error:

This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Reinstalling the application may fix this problem.


which is typically attributed to the Qt plugins not being found. Looking
at the bin folder, I saw that the Qt libraries are shipped in the binary
package, but not the required Qt plugins. Is there a particular reason
for that?

In my view, you should either ship a complete self-contained set of Qt
libraries, or none at all. After I deleted all bin/libQt5* files, my
system Qt libraries were used by the MITK Workbench and hence also the
system Qt plugins were found and loaded (sure, some QT_PLUGIN_PATH env
var trickery would also work, but just hides the real issue). The
workbench started just fine.

Let me know if I can help with this for the next release.

Thanks,

Sascha
Dinkelacker, Stefan
2017-07-18 07:32:07 UTC
Permalink
Hi Sascha,

you're right. It wasn't intended not to ship the Qt plugins within the package. I'll check that and update the tarball. BTW, do you know something similar for Linux like windeployqt.exe?

Best,
Stefan

-----Original Message-----
From: Sascha Zelzer [mailto:***@gmail.com]
Sent: Montag, 17. Juli 2017 18:40
To: mitk-***@lists.sourceforge.net
Subject: [mitk-users] Linux package contains Qt libraries but no plugins

Hi,

I just tried the MITK 2016.11 Linux binary (I have a MR dicom series to
view) and got the (kind of) common error:

This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Reinstalling the application may fix this problem.


which is typically attributed to the Qt plugins not being found. Looking at the bin folder, I saw that the Qt libraries are shipped in the binary package, but not the required Qt plugins. Is there a particular reason for that?

In my view, you should either ship a complete self-contained set of Qt libraries, or none at all. After I deleted all bin/libQt5* files, my system Qt libraries were used by the MITK Workbench and hence also the system Qt plugins were found and loaded (sure, some QT_PLUGIN_PATH env var trickery would also work, but just hides the real issue). The workbench started just fine.

Let me know if I can help with this for the next release.

Thanks,

Sascha


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________
mitk-users mailing list
mitk-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users
Sascha Zelzer
2017-07-19 06:23:06 UTC
Permalink
Hi Stefan,

there is linuxdeployqt, but it seems to have a couple of issues. With
the plugins, one would either need to copy all the plugins from the
build machine, or have a curated list of plugins required for the
application to work. No tool can possibly infer plugin dependencies
without knowledge of the source code or runtime behavior.

Best,

Sascha
Post by Dinkelacker, Stefan
Hi Sascha,
you're right. It wasn't intended not to ship the Qt plugins within the package. I'll check that and update the tarball. BTW, do you know something similar for Linux like windeployqt.exe?
Best,
Stefan
-----Original Message-----
Sent: Montag, 17. Juli 2017 18:40
Subject: [mitk-users] Linux package contains Qt libraries but no plugins
Hi,
I just tried the MITK 2016.11 Linux binary (I have a MR dicom series to
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".
Reinstalling the application may fix this problem.
which is typically attributed to the Qt plugins not being found. Looking at the bin folder, I saw that the Qt libraries are shipped in the binary package, but not the required Qt plugins. Is there a particular reason for that?
In my view, you should either ship a complete self-contained set of Qt libraries, or none at all. After I deleted all bin/libQt5* files, my system Qt libraries were used by the MITK Workbench and hence also the system Qt plugins were found and loaded (sure, some QT_PLUGIN_PATH env var trickery would also work, but just hides the real issue). The workbench started just fine.
Let me know if I can help with this for the next release.
Thanks,
Sascha
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________
mitk-users mailing list
https://lists.sourceforge.net/lists/listinfo/mitk-users
Loading...