TheAssassin
Appimages crash when appimagelauncher is installed
Pre-submit checks
- [x] 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.
- [x] 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
I installed AppImageLauncher and tried to run my software, https://ossia.io through it following bug reports.
This causes the following issue:
$ ./ossia.score-master-linux-x86_64.AppImage
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
Can't open squashfs image: Bad address
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
execv error: No such file or directory
Also mentioned here: https://github.com/probonopd/go-appimage/issues/242
what's the solution for this?
Expected behavior
Any AppImage that runs without AppImageLauncher is not broken by it
Steps to reproduce the issue
- Download some appimage, e.g. https://github.com/ossia/score/releases/download/v3.4.1/ossia.score-3.4.1-linux-amd64.AppImage
- Try to run it with AppImageLauncher running
- It does not work
Screenshots
No response
Distribution and desktop environment
ArchLinux, i3
Installed AppImageLauncher version
AppImageLauncher version 2.2.0 (git commit 0f91801), built on 2024-05-25 20:37:48 UTC
List of AppImages you tried
- Krita (works) - https://download.kde.org/stable/krita/5.2.9/krita-5.2.9-x86_64.AppImage
Additional context
No response
Looks like a duplicate of https://github.com/TheAssassin/AppImageLauncher/issues/585 Try using AppImageLauncher version v3.0.0-alpha-3 or later.
I mean I'm not even using Appimage launcher myself, but people have it installed on their computer, then launch my software and it crashes (and i get the bug reports)
I had this bug as well. I do love this utility, but would suggest that it clearly outputs that the error comes from it. I kept thinking it was the appimage that had problems even though I launched from commandline, not suspecting the utility. This sent me down the wrong path with troubleshooting for two days. A clear message that the utility activated and ran into problems would be enough to set people on the right path.
I mean I'm not even using Appimage launcher myself, but people have it installed on their computer, then launch my software and it crashes (and i get the bug reports)
The issue here is the introduction of the new static type-2 runtime for which this software wasn't quite prepared. There is nothing we can do to show a proper error message, as the way the new runtime fails with the old version is unexpected and therefore not handled accordingly. Among other things, the new 3.0.0 release improves this behavior.
As suggested by @JulianGro, version 3.0.0 fixes the problem and works reliably even if the release is still labeled alpha.