Sascha Zelzer
2017-07-17 16:40:08 UTC
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
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