* claim: #4640 * Docs: AppImageLauncher 2.x can't start the AppImage; update to 3.0 (#4640) AppImageLauncher 2.x intercepts every AppImage through binfmt_misc and can't start static-runtime AppImages such as SolidCraft's: it fails with "execv error: No such file or directory" after a FUSE message. 3.0 starts it. One paragraph in the Linux AppImage section says so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Docs: AppImageLauncher 3.0 is so far only published as betas (#4640) Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com>
This commit is contained in:
1 file changed
+5
@@ -37,6 +37,11 @@ started it (and removes the entry SolidCraft added before). To
|
||||
turn it off for good, create an empty file `~/.local/share/solidcraft/no-desktop-integration`, or
|
||||
start the AppImage with `SOLIDCRAFT_NO_DESKTOP_INTEGRATION=1`.
|
||||
|
||||
If the AppImage doesn't start and prints a FUSE message followed by `execv error: No such file
|
||||
or directory`, AppImageLauncher 2.x is intercepting it: it can't start AppImages built on the
|
||||
static runtime, as SolidCraft's is. Update AppImageLauncher to 3.0 (so far only published as
|
||||
betas; 3.0.0-beta-3 or newer works), or remove it.
|
||||
|
||||
### Linux Flatpak
|
||||
|
||||
Install Flatpak using your distribution's package manager. For an installation that receives
|
||||
|
||||
Reference in new issue
Block a user