Skip to content

docs: correct the Linux AppImage runtime dependency #1799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mrhy7176 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: correct the Linux AppImage runtime dependency #1799

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/getting-started/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ chmod +x StabilityMatrix.AppImage
./StabilityMatrix.AppImage
```

Depending on the distribution, AppImage runtime support packages may still be required. The current repo and docs specifically call out `libfuse2`, and on some systems `libappimage` or `libxcrypt-compat` may also be needed.
Depending on the distribution, AppImage runtime support packages may still be required. Releases since 2.16.2 use a FUSE3-based runtime and no longer need `libfuse2` (`libfuse.so.2`), which current distributions such as Ubuntu 24.04+ and Fedora 40+ do not ship. On a minimal system, install `fuse3` so `fusermount` or `fusermount3` is available, or start the AppImage with `--appimage-extract-and-run` when FUSE is not installed. Some distributions also need `libxcrypt-compat`. See the [2.16.2 release notes](../release-notes/2.16.2.md#linux-appimage).

Arch-based users can also use the [AUR package](https://aur.archlinux.org/packages/stabilitymatrix), but it comes with a few practical differences from the standalone AppImage release. The AUR build is typically installed under `/opt`, cannot update itself through Stability Matrix's in-app updater, and instead must be updated through the AUR package as part of normal system package maintenance. There can also be a delay between a new Stability Matrix release and the corresponding `PKGBUILD` update in AUR. If that delay is a problem, or if `/opt` ownership and file-permission behavior causes update or launch issues, the standalone AppImage release is the safer option.

Expand Down
2 changes: 1 addition & 1 deletion docs/troubleshooting/common-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ This means the workload exceeded your available VRAM, not a Stability Matrix bug
## Linux and macOS

**The Linux AppImage will not run on some distributions.**
The AppImage may need runtime support packages such as `libfuse2` (and, depending on the distribution, ICU or related libraries) that are not installed by default. This and the `.desktop` and AUR quirks are covered in [Installation → Linux](../getting-started/installation.md#linux).
Current releases use a FUSE3 runtime and do not need `libfuse2`. On a minimal system, install `fuse3` (providing `fusermount` or `fusermount3`), or launch with `--appimage-extract-and-run` if FUSE is unavailable. Depending on the distribution, ICU or related libraries may also be required. Desktop-entry and AUR details are in [Installation → Linux](../getting-started/installation.md#linux).

**macOS Gatekeeper blocks the first launch.**
This is expected for a downloaded app. The steps to allow it are in [Installation → macOS](../getting-started/installation.md#macos).
Expand Down
Loading