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

[probonopd]

We have something that begins to launch now, but:

$ Downloads/Lector-ff03947-x86_64.AppImage 
(...)
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.
Aborted
me@host:~$ LD_DEBUG=libs Downloads/Lector-ff03947-x86_64.AppImage 2<&1 | grep init: /usr
grep: /usr: Is a directory
me@host:~$ LD_DEBUG=libs Downloads/Lector-ff03947-x86_64.AppImage 2<&1 | grep "init: /usr"
     10760:	calling init: /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
     10760:	calling init: /usr/lib/x86_64-linux-gnu/libX11.so.6
     10760:	calling init: /usr/lib/x86_64-linux-gnu/libGLX.so.0
     10760:	calling init: /usr/lib/x86_64-linux-gnu/libXext.so.6
     10760:	calling init: /usr/lib/x86_64-linux-gnu/libGL.so.1
me@host:~$ LD_DEBUG=libs Downloads/Lector-ff03947-x86_64.AppImage 2<&1 | grep "init: /lib"
     10774:	calling init: /lib/x86_64-linux-gnu/libpthread.so.0
     10774:	calling init: /lib/x86_64-linux-gnu/libc.so.6
     10774:	calling init: /lib/x86_64-linux-gnu/libz.so.1
     10774:	calling init: /lib/x86_64-linux-gnu/libdl.so.2
     10774:	calling init: /lib/x86_64-linux-gnu/libfuse.so.2
     10774:	calling init: /lib/x86_64-linux-gnu/libc.so.6
     10774:	calling init: /lib/x86_64-linux-gnu/libdl.so.2
     10774:	calling init: /lib/x86_64-linux-gnu/libtinfo.so.5
     10783:	calling init: /lib/x86_64-linux-gnu/libc.so.6
     10781:	calling init: /lib/x86_64-linux-gnu/libc.so.6
     10774:	calling init: /lib/x86_64-linux-gnu/libpthread.so.0
     10774:	calling init: /lib/x86_64-linux-gnu/libc.so.6
     10774:	calling init: /lib/x86_64-linux-gnu/libm.so.6
     10774:	calling init: /lib/x86_64-linux-gnu/librt.so.1
     10774:	calling init: /lib/x86_64-linux-gnu/libutil.so.1
     10774:	calling init: /lib/x86_64-linux-gnu/libdl.so.2

Not sure what is going on here... ping @TheAssassin any idea?

[TheAssassin]

I've got no idea. CC @TheLastProject do you remember whether we've had a bug like that while bundling Pext?

[TheLastProject]

Maybe Pext/Pext#99?

[TheAssassin]

@TheLastProject that looks good, thanks!

@probonopd please add xorg-libxi to your conda packages.

[probonopd]

Thanks @TheLastProject and @TheAssassin. Turns out that it is looking for the Qt plugins in an entirely wrong directory.

( cd squashfs-root/usr/conda/bin/ ; ln -s ../plugins/platforms/ . ) was needed to "fix" this. I don't assume that this is a Lector-specific issue, it's probably more a Qt-in-Conda thing?

[TheAssassin]

The conda Qt packages are broken in many ways. Try to use PyQt5 from PyPI directly.

[probonopd]

This is what I was using so far:

export APPNAME=lector
export PIP_REQUIREMENTS="-e git+https://github.com/BasioMeusPuga/Lector#egg=$APPNAME"
export CONDA_CHANNELS="conda-forge"
export CONDA_PACKAGES="pyqt;beautifulsoup4;xorg-libxi"  # Only use this if the package is in a Conda channel (e.g., conda-forge); can also be used for dependencies if the main application has no depends.txt

[probonopd]

Much better now @TheAssassin. 👍 This should be documented, and possibly a bug be filed against Qt from conda-forge.