Flameshot AppImage doesn't start, squashfs image uses (null) compression

[bmondream]

Pre-submit checks

• I checked for similar issues beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue.
• I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.

Describe the bug

When I run Flameshot v11.0 AppImage via AppImageLauncher, it opens just fine. But Flameshot v12.0 and higher doesn't start (but starts just fine without using AppImageLauncher):

$ ./Flameshot-11.0.0.x86_64_22c672af70319f3838c53e2689f2711b.AppImage
Failed to get information about the latest version.  "Host api.github.com not found"
Failed to get information about the latest version.  "Host api.github.com not found"
QPainter::begin: Paint device returned engine == 0, type: 2
^C

$ ./Flameshot-12.0.rc1.x86_64_33327c82e1c11c0783945e9d575495ac.AppImage
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_shall_not_be_integrated : sqfs_open_image error: /home/user/Applications/Flameshot-12.0.rc1.x86_64_33327c82e1c11c0783945e9d575495ac.AppImage
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1) 
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_is_terminal_app : sqfs_open_image error: /home/user/Applications/Flameshot-12.0.rc1.x86_64_33327c82e1c11c0783945e9d575495ac.AppImage
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1) 
execv error: No such file or directory

$ ./Flameshot-12.1.0.x86_64_10ab227368a704f2d66cded7a7aa8248.AppImage
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_shall_not_be_integrated : sqfs_open_image error: /home/user/Applications/Flameshot-12.1.0.x86_64_10ab227368a704f2d66cded7a7aa8248.AppImage
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1) 
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_is_terminal_app : sqfs_open_image error: /home/user/Applications/Flameshot-12.1.0.x86_64_10ab227368a704f2d66cded7a7aa8248.AppImage
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1) 
execv error: No such file or directory

Expected behavior

Flameshot v12.0 AppImage and higher opens successfully.

Steps to reproduce the issue

1. Download Flameshot AppImage either v12.0 or v12.1
2. Run the AppImage (from the terminal to see the error log) while AppImageLauncher is running
3. Click either Integrate and run or Run once
4. This GUI error dialog is displayed:
   
   and the terminal shows the error messages I mentioned above

Screenshots

No response

Distribution and desktop environment

OS: Kubuntu 22.04.3 LTS x86_64
DE: Plasma 5.24.7

Installed AppImageLauncher version

AppImageLauncher version 2.2.0 (git commit d9d4c73), built on 2022-09-08 14:49:51 UTC

List of AppImages you tried

Flameshot v12.0 and v12.1 doesn't work, but Flameshot v11.0 does

Additional context

I'm not entirely sure whether this is a bug in AppImageLauncher. But again, it works without the launcher.
I looked through the code to find what's causing the appimage_shall_not_be_integrated error and it seems there must be X-AppImage-Integrate=false set somewhere, but I haven't found it in Flameshot's GitHub repository. In any case, can't this be overridden with a CLI argument to integrate it regardless of whether that option is set?

[tneo]

I have the same error message with the latest pcloud 1.14.1 instance, the 1.14.0 version did work. I was forced to remove AppImageLauncher, otherwise I could no longer access my files.

Operating System: openSUSE Tumbleweed 20231016
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.6-1-default (64-bit)
Graphics Platform: Wayland

[manjarooo]

I also have the same error message (execv error: No such file or directory), with the latest Shotcut 23.09.29 AppImage :
https://shotcut.org/download/
The app doesn't start, and the integration process also couldn't integrate the AppImage into the system (file has been copied to folder, but no menu entry generated). And every time I restart the AppImage, I get asked again and again if I want to start or integrate.

Previous versions worked well, for example Shotcut version 23.07.29. The only problem here was, that the app icon on the applications menu entry was missing.
I have tried to deactivate appimagelauncherd with its configuration app, and with "systemctl disable --user appimagelauncherd.service", but the only working solution was to uninstall AppImageLauncher completely!

My OS: Debian Linux 12 (bookworm)
with MATE Desktop 1.26.0
and Qt 5.15.8
Kernel: 6.1.55-1 (x86_64)

[smacz42]

I had the same issue with Manager.io: https://forum.manager.io/t/appimage-lastest-version-different-to-september-23/49367/12

Uninstalling AppImageLauncher and rebooting and executing the appimage directly worked. Obviously not ideal, however.

[rollerozxa]

I'm having this same issue with an AppImage I have built myself with appimagetool. It appears that by default appimagetool uses Zstd compression for squashfs, as can be seen in the build output for my AppImage:

Exportable Squashfs 4.0 filesystem, zstd compressed, data block size 1048576

Zstd compression works fine when running the generated AppImage standalone but it appears that AppImageLauncher does not support AppImages with Zstd compression, because as the console output says it only supports LZMA compression and zlib:

Squashfs image uses (null) compression, this version supports only xz, zlib.

AppImageLauncher would need to be updated to support Zstd, unsure why it still doesn't support it yet (is AppImageLauncher still maintained?). But for now AppImage authors need to use another compression format than the default one by passing either --comp xz or --comp gzip to appimagetool to have it work with AppImageLauncher.

[noanight]

fails too....with Librecad

user@host:~/Applications$ ./LibreCAD-2.2.1_rc2-8-g0649fad1-x86_64_53e9c1c6da66324d70ba73d804791d59.AppImage
execv error: No such file or directory

user@host:~/Applications$ ./LibreCAD-2.2.0.2-14-g10ad9444-x86_64_22d2293bc471b1438e8bb41cfd370197.AppImage
execv error: No such file or directory

user@host:~/Applications$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy

uninstalled AppImageLauncher and both LibreCAD Images start...

[vanboom]

Fails also with Postman https://github.com/suciptoid/postman-appimage/releases on Debian 12

Squashfs image uses (null) compression, this version supports only xz, zlib.
...
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)
execv error: No such file or directory

[citkane]

Appimagelauncher release build (v2.2.0)

I can confirm the same for me with Librecad;

michaeladmin@HTPC:~/.local/share/applications$  lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 12 (bookworm)
Release:	12
Codename:	bookworm

michaeladmin@HTPC:~/.local/share/applications$ ./LibreCAD-2.2.1_rc3-30-gcd7bd7b9-x86_64_854b49e80b27e4a4ab2b50a87708fd5f.AppImage 
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_shall_not_be_integrated : sqfs_open_image error: /home/michaeladmin/.local/share/applications/LibreCAD-2.2.1_rc3-30-gcd7bd7b9-x86_64_854b49e80b27e4a4ab2b50a87708fd5f.AppImage
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_is_terminal_app : sqfs_open_image error: /home/michaeladmin/.local/share/applications/LibreCAD-2.2.1_rc3-30-gcd7bd7b9-x86_64_854b49e80b27e4a4ab2b50a87708fd5f.AppImage
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)
execv error: No such file or directory

[adrianinsaval]

latest appimagetool builds use zstd by default but it seems this is not supported by appimagelauncher, is this project still relevant and maintained @TheAssassin ?

[fangly]

I have the exact same issue with the latest FreeCAD AppImage, FreeCAD_1.0.0RC4-conda-Linux-x86_64-py311_0445d5476aa3d331ef8912858f3fd28d.AppImage

[cwgstreet]

I have the exact same issue with the latest FreeCAD AppImage, FreeCAD_1.0.0RC4-conda-Linux-x86_64-py311_0445d5476aa3d331ef8912858f3fd28d.AppImage

Same here with the above FreeCad 1RC4 appimage file. I haven't yet found a way around this other than uninstalling appimage launcher

[Norbert-Rotorwerk]

This is an issue of AppimageLauncher. Removing AppimageLauncher is the solution. There is a bug report in AppimageLauncher describing the problem #674

[rollerozxa]

This is an issue of AppimageLauncher. Removing AppimageLauncher is the solution. There is a bug report in AppimageLauncher describing the problem #674

In fact, the issue tracker seems to be flooding with AppImageLauncher users running into this now 😅

To be honest, from the point of a developer making AppImages, when I first ran into this issue I thought it was on me since I was originally using appimagetool from https://github.com/AppImage/appimagetool which only supports zstd compression, and thought this was some weird unstable version I shouldn't be using, and moved over to the one found in AppImageKit that supports xz and gzip thinking that's the one I should be using. But now that one is apparently obsolete and there is no way to make an AppImage with a non-obsolete appimagetool that is supported by AppimageLauncher. I don't really know what to make of this.