Lukas Spies

If I use an old AppImage from right before when this started (downloaded from here, found this link in another issue: https://artifacts.assassinate-you.net/artifactory/list/linuxdeploy/travis-456/) everything still works, so something got added/changed after...

I just tried it with the latest continuous build and it still fails with the same error.

Sure, no problem: ``` $ QML_SOURCES_PATHS=./qml ./squashfs-root/AppRun --appdir ./appdir/ -d ./appdir/usr/share/applications/myapplication.desktop --plugin=qt --output appimage -v0 linuxdeploy version 1-alpha (git commit ID 3e05627), Travis build 490 built on 2020-11-18 18:21:58 UTC...

Sure, let me try this.

Unfortunately there doesn't seem to be any debug info available: ``` terminate called after throwing an instance of 'std::logic_error' what(): subprocess failed (exit code 1) Program received signal SIGABRT, Aborted....

Hm, that is indeed odd. Even if I run it without any options (i.e., simply `./squashfs-root/AppRun`) it gives the same crash...

If I do the same steps in an Ubuntu bionic docker container I get the exact same error.

Thanks for looking into it @TheAssassin ! I don't know if that adds potential confusion again: If I build an AppImage today using a build of linuxdeploy from back in...

Sorry, here we go: Running the plugin in a docker contaner running ubuntu xenial works just fine: ``` # ./squashfs-root/usr/bin/linuxdeploy-plugin-qt --plugin-api-version 0 ``` Patching out the magic bytes using the...

If I remove the qt plugin then linuxdeploy starts out just fine doing a bunch of stuff until it eventually expectedly fails with `ERROR: Could not find plugin: qt`. If...