Open bmondream opened 1 year ago
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
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)
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.
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.
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...
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
Pre-submit checks
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):
Expected behavior
Flameshot v12.0 AppImage and higher opens successfully.
Steps to reproduce the issue
Integrate and run
orRun once
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 beX-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?