Will SoloMD run on my Linux?

Almost any Linux released since 2022 works out of the box; the ones that don’t are older systems. Follow the chart below — it takes about two minutes and also tells you which file to download.

The whole thing in one chart

1. 1
   Open a terminal

   Search your app menu for “Terminal”, or press Ctrl + Alt + T.

3. 2
   Type this line and press Enter

   ldd --version

   Look only at the number at the very end of the first line, for example:

   ldd (Ubuntu GLIBC 2.35-0ubuntu3.8) 2.35

5. Is that number 2.34 or higher?

   2.35, 2.36, 2.39 all count as “yes”; 2.31, 2.28, 2.17 count as “no”.

6. No

   This system is too old

   SoloMD can’t run on it yet — no download will change that. The fix is to upgrade to a release marked ✅ in the table below.

   See which release to upgrade to ↓
   Yes

   You’re good 👍

   Go on to step 3 and pick a file.

   Step 3 ↓

sudo apt install ./SoloMD_*.deb

sudo dnf install ./SoloMD-*.rpm

yay -S solomd-bin

chmod +x SoloMD_*.AppImage && ./SoloMD_*.AppImage

Every file comes in two builds. Most computers want amd64 / x86_64; ARM machines such as a Raspberry Pi want arm64 / aarch64. Not sure? Run uname -m — if it prints aarch64, it’s ARM.

Rather not type commands? Look it up

These are the common ones. If yours isn’t listed, or you’ve customised your system, trust the ldd check above.

Why don’t older systems work?

SoloMD doesn’t ship a whole user-interface stack of its own. It borrows two things your system already has: a “web engine” that draws the window (WebKitGTK) and the “base library” every program uses (glibc). Think of furniture that mounts on a wall — the wall needs the right brackets.

Systems from around 2022 onward have the brackets we need: glibc 2.34 or newer and WebKitGTK 4.1. Older systems have versions that are too low, or no such web engine at all. That floor comes from the framework SoloMD is built on (Tauri 2) — it isn’t a number we can simply turn down — so upgrading the system is the only reliable fix. The AppImage carries its own web engine, so it needs one thing less than .deb / .rpm, but it can’t carry the base library.

Followed the chart and it still fails?

Please open an issue on GitHub and paste the output of these three commands — it lets us tell what’s wrong quickly:

ldd --version | head -1
grep PRETTY_NAME /etc/os-release
uname -m