From 1d482aff748a6889cbff076bfcc87da6635ef59e Mon Sep 17 00:00:00 2001 From: Logan Night <96597232+flyboy-byte@users.noreply.github.com> Date: Mon, 26 Oct 2026 06:49:52 +0000 Subject: [PATCH] Docs: AppImageLauncher 2.x can't start the AppImage; update to 3.0 (#4640) (#4674) * 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 * 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 --------- Co-authored-by: Claude Opus 5.5 Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com> --- docs/book/src/guide/getting-started.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/book/src/guide/getting-started.md b/docs/book/src/guide/getting-started.md index ab474a60b..4481e9b44 100644 --- a/docs/book/src/guide/getting-started.md +++ b/docs/book/src/guide/getting-started.md @@ -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