How to Install OrcaSlicer on Linux: AppImage, Flatpak, AUR

by
TL;DR: Three ways to put OrcaSlicer on a Linux box, ranked by sanity. AppImage stays portable, Flatpak handles sandboxing, AUR is for Arch loyalists. Wayland and GLIBC 2.38 gotchas included.

The first time I installed OrcaSlicer on Linux, it was a fresh Debian 12 box, and I got a confident “Permission denied” the second I double-clicked the AppImage. Two minutes later, after I’d chmod’d it executable, I got the famous “dlopen(): error loading libfuse.so.2” splash, which is Linux’s special way of saying “welcome, please read the docs.”

I’ve since installed OrcaSlicer on Ubuntu 22.04, Ubuntu 24.04, Pop!_OS, Fedora Workstation, EndeavourOS, and a Steam Deck in desktop mode, and every single one wanted something slightly different. That’s Linux installs in a nutshell: there isn’t one path, there are three, and the right one depends on your distro, your GPU, and how much you care about sandboxing. This guide walks you through all three official routes (AppImage, Flatpak, AUR) with the exact gotchas I’ve hit on real machines in 2026.

Table of contents

The Linux install picture in 2026, three routes, one binary

Here’s the situation. OrcaSlicer publishes three official Linux artifacts per release on GitHub, and there’s a community-maintained set of AUR packages for the Arch crowd. There’s no Snap, no signed .deb in the official assets, no .rpm, and no system tray installer that does everything for you. You pick the route that fits your distro and your tolerance for sandboxing.

The three real options are the AppImage (the portable single-file binary), the Flatpak from Flathub (sandboxed, bundled runtime, cross-distro), and the AUR packages (if you’re on Arch or a derivative). I’ll walk through each one in detail, but if you just want a recommendation right now, here’s the short version: if you’re on a current Ubuntu, Pop!_OS, or Mint, the AppImage is fastest. If you’re on Debian 12, an older Mint, Zorin, or anything immutable like Fedora Silverblue, jump straight to Flatpak. If you’re on Arch, you already know to check the AUR.

One thing worth flagging up front, because it bit me hard and it’s biting a lot of people in 2026: the official AppImage filename literally includes Ubuntu2404 because that’s the build host. That means it’s linked against GLIBC 2.38 or newer, and if you’re on Debian 12 (GLIBC 2.36), Linux Mint 21, or Zorin OS 17.x (Ubuntu 22.04 base), the AppImage will refuse to launch. There’s a verified GitHub issue (#10990) tracking this. We’ll come back to it, but Flatpak is the answer if you’re stuck.

Pick your route, a quick chooser

Before we get into the commands, let me save you ten minutes of guessing. Here’s how I’d pick if I were standing in front of your machine.

  • You’re on current Ubuntu (24.04+), Pop!_OS 24.04, or Mint 22: AppImage works fine, install libfuse2t64, and you’re done in under a minute.
  • You’re on Ubuntu 22.04 LTS: AppImage works, but install libfuse2 instead (different package name on this release). Still fast.
  • You’re on Debian 12, Linux Mint 21, Zorin 17.x, or anything with GLIBC older than 2.38: skip the AppImage entirely. Use the Flatpak. It bundles its own runtime so your host GLIBC version stops mattering.
  • You’re on Fedora, Fedora Silverblue, Kinoite, openSUSE, NixOS, or any immutable distro: Flatpak. It’s not even close.
  • You’re on Arch, Manjaro, or EndeavourOS: AUR. Specifically orca-slicer-bin unless you have a reason to compile from source.
  • You’re running NVIDIA proprietary drivers + Wayland session: any install route works, but you’ll likely need to log out and pick the X11/Xorg session at your display manager. More on that in the Wayland section.

That’s the cheat sheet. Now let’s get into each route.

Route 1, AppImage: the official portable binary

The AppImage is OrcaSlicer’s flagship Linux artifact. It’s a single file (~125 MB), ships with everything it needs except FUSE2 and a recent enough GLIBC, and you don’t have to install it system-wide. I keep mine in ~/Applications/ and that’s it.

Grab it from the canonical GitHub releases page: github.com/SoftFever/OrcaSlicer/releases. As of v2.3.2 the asset you want is OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.2.AppImage. Don’t grab anything off random mirrors. The GitHub releases page is the only canonical source.

Once it’s downloaded, here’s the three-step incantation. Open a terminal in your downloads folder and run:

chmod +x OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.2.AppImage
./OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.2.AppImage

If it launches, you’re done. If it doesn’t, you’ve hit one of two things: the FUSE error, or the GLIBC error. They look different. Let’s handle them.

The FUSE error: pick the right package for your Ubuntu version

If your terminal spits back something like dlopen(): error loading libfuse.so.2 AppImages require FUSE to run, that’s because Ubuntu (and a lot of derivatives) stopped shipping libfuse2 by default a couple of years back. AppImages still need FUSE2 specifically (not FUSE3, which is a different thing entirely, despite the name). The fix is one package, but the name depends on your Ubuntu release:

  • Ubuntu 22.04 LTS (and derivatives based on it, like Pop!_OS 22.04 and Mint 21): sudo apt install libfuse2
  • Ubuntu 24.04+ (and Pop!_OS 24.04, Mint 22): sudo apt install libfuse2t64

That t64 suffix isn’t a typo, it’s the 64-bit time_t transition that Debian and Ubuntu pushed through in 2024, and a bunch of library packages got renamed as part of it. FUSE2 and FUSE3 happily coexist, so installing libfuse2t64 won’t break anything else on your system that needs FUSE3. The OrcaSlicer team marked their original FUSE issue (#5482) as “not planned” because this is fundamentally an AppImage runtime requirement, not something OrcaSlicer can fix at their end. The official AppImage troubleshooting docs are the canonical reference if you want to read more.

Desktop integration, optional but nice

A raw AppImage doesn’t show up in your application menu by default. If you want the OrcaSlicer icon in your launcher (and you probably do), install AppImageLauncher from your distro’s repos. It handles registration, icon extraction, and updates automatically. You don’t strictly need it, but I run it on every Linux machine I own because clicking an icon beats cd ~/Applications && ./Orca* every time.

If you don’t want AppImageLauncher, you can create a .desktop file by hand in ~/.local/share/applications/, but honestly, just install the launcher. It’s five MB.

Route 2, Flatpak from Flathub: the easiest cross-distro path

If you’re on an older Ubuntu derivative, Debian, Fedora, anything immutable, or you just like the idea of sandboxed apps, Flatpak is the path of least resistance. The OrcaSlicer team published the official Flathub listing as of v2.3.2, and the bundled runtime means your host distro’s GLIBC version stops mattering entirely. That’s huge if you’ve been chasing GLIBC errors on the AppImage.

Before you can install anything from Flathub, you need to enable the Flathub remote on your distro. The Flathub setup pages cover this for every major distro, but the rough shape is:

  • Ubuntu / Pop!_OS / Mint: install flatpak from apt, then add the Flathub remote (the Flathub Ubuntu setup page walks you through it).
  • Debian: the Flathub Debian setup page covers the apt commands.
  • Fedora: Flathub is already configured out of the box on Workstation, Silverblue, and Kinoite. Skip this step.
  • Arch: the Flathub Arch setup page has the pacman commands.

Once Flathub is enabled, the install is a single command. This is the part where the app ID change matters, so pay attention. The new canonical Flatpak ID, as of v2.3.2, is com.orcaslicer.OrcaSlicer. Older guides (and the original Flathub discussion thread) mention io.github.softfever.OrcaSlicer, which was the legacy ID. The v2.3.2 release notes explicitly call out that migration code is included, but for fresh installs you should always use the new one.

flatpak install flathub com.orcaslicer.OrcaSlicer
flatpak run com.orcaslicer.OrcaSlicer

That’s it. The download is about 166 MiB (it pulls in the runtime if it isn’t cached), and after first launch it’ll show up in your application menu like a native app. The Flathub listing shows around 22,000 downloads a month, so this is a well-trodden path.

Sandbox basics, and what to do if your printer’s invisible

Flatpak runs sandboxed, which is great for security but occasionally awkward if your printer is on USB or your LAN and OrcaSlicer can’t see it. The standard troubleshooting move is to grant filesystem or device access with flatpak override. For example, to give OrcaSlicer access to your full home directory, you’d run flatpak override --user --filesystem=home com.orcaslicer.OrcaSlicer. For USB devices, the override target is --device=all (broad) or you can scope it tighter. I’d start narrow and widen only if you have to.

That said, in my experience the default Flatpak permissions handle network printer discovery just fine on Bambu and Klipper setups. I’ve only had to override permissions when I was doing something unusual, like pointing OrcaSlicer at an SD card mounted in /media.

Route 3, AUR for Arch, Manjaro, EndeavourOS

If you’re on an Arch-based distro, the AUR is where you live, and OrcaSlicer is well-represented there. There are five packages worth knowing about, and the names all use the hyphenated form (orca-slicer, not orcaslicer). Don’t waste five minutes searching for orcaslicer-bin, it doesn’t exist.

  • orca-slicer-bin: the pre-compiled binary, maintained by JoveYu. Currently at 2.3.2-3 with 24 votes. This ships the official AppImage repackaged. Fastest install.
  • orca-slicer: the source build, maintained by c2h5oh. Currently at 1:2.3.2-6, with 37 votes. 39 dependencies. The PKGBUILD uses CMAKE_BUILD_PARALLEL_LEVEL = min(CPU, RAM_GB/2) to keep your machine from OOM’ing during the compile, which is a nice touch if you’ve got 8 or 16 GB of RAM.
  • orca-slicer-git: bleeding-edge, builds from the latest commit. Use if you’re chasing a fix that hasn’t shipped yet.
  • orca-slicer-nightly-bin: pre-built nightly AppImage, repackaged for Arch.
  • orca-slicer-unstable-bin: the unstable channel binary.

For 99% of people I’d just go with orca-slicer-bin. If you’ve got paru or yay set up, it’s one command:

paru -S orca-slicer-bin

Or with yay:

yay -S orca-slicer-bin

The dependency list is worth peeking at: cairo, glu, gstreamer, gtk3, libice, libmspack, libsm, mesa-utils, wayland, webkit2gtk-4.1. Two of those have caused people grief on Arch in particular. If you get a shared-library load error after install, double-check that libmspack is present from the official repo. And mesa-utils isn’t optional, because the startup script calls glxinfo to detect your GPU. Without it, the launcher just dies silently. The maintainer notes this in the package comments.

License-wise, the source package is tagged AGPL-3.0-only, which matches OrcaSlicer’s overall license. You can browse the full AUR listings for orca-slicer to see all five packages and their stats.

Where OrcaSlicer stores your profiles on Linux

This matters because if you ever want to back up your printer profiles, migrate to another machine, or recover after a borked install, you need to know where the config lives. The path depends on how you installed it.

  • Native (AppImage, AUR, or built from source): ~/.config/OrcaSlicer/
  • Flatpak (new ID, v2.3.2+): ~/.var/app/com.orcaslicer.OrcaSlicer/config/OrcaSlicer/
  • Flatpak (legacy ID, pre-v2.3.2 installs): ~/.var/app/io.github.softfever.OrcaSlicer/config/OrcaSlicer/

If you had a Flatpak install before v2.3.2 and you upgraded, you might find your profiles in the legacy path. The v2.3.2 release notes mention that migration code is included, but I’d back up both locations before you trust anything important to the migration. Copy the whole folder to an external drive or cloud sync, then upgrade.

The reference for these paths is OrcaSlicer’s own Discussion #1594, which the maintainers use as the canonical config-location thread. If you want a deeper walkthrough on backing up and restoring profiles when you update, we’ve got a dedicated guide on updating OrcaSlicer without losing your profiles that covers the migration moves in detail.

The GLIBC 2.38 gotcha, why your AppImage won’t launch on Debian 12

This is the single most reported install problem in 2026, so it gets its own section. The OrcaSlicer team builds the official AppImage on Ubuntu 24.04, which links against GLIBC 2.38. If your host distro ships an older GLIBC, the AppImage will fail to start with a cryptic error along the lines of GLIBC_2.38' not found.

Verified-affected distros from issue #10990 (linked in the intro):

  • Debian 12 Bookworm (GLIBC 2.36): fails.
  • Linux Mint 21: fails.
  • Zorin OS 17.3 (Ubuntu 22.04 base): fails.

The fix is straightforward: don’t fight it, just use the Flatpak. The Flatpak bundles its own runtime, so the host’s GLIBC version is irrelevant. If for some reason you absolutely have to run an AppImage (say, you’re locked into an air-gapped environment with no Flathub access), you can fall back to v2.3.0, which was built on Ubuntu 20.04 and has a much older GLIBC floor. But really, just use Flatpak.

A weird related thing: even Arch Linux users with GLIBC 2.42 have reported the AppImage failing to launch. That’s not a GLIBC problem, it’s most likely a conflicting libstdc++ pulled in at runtime, but the symptom looks the same. On Arch, use the AUR package instead. The Manjaro KDE 6.3.6 reporter in that issue thread confirmed it works there, so it’s not a fundamental Arch problem, just an AppImage portability one.

Wayland vs X11, the one thing that breaks for NVIDIA users

If you’re on NVIDIA’s proprietary driver and a Wayland session, OrcaSlicer is going to have a bad time. This isn’t FUD, it’s documented across at least seven open issues on the OrcaSlicer tracker as of mid-2026, and it spans multiple distros and driver versions. The symptoms range from a missing build plate preview to outright crashes when slicing detailed models.

The verified open issues, if you want to read the gory details:

  • #8145: build plate preview completely missing under Wayland + NVIDIA proprietary
  • #11722: crashes under KDE Plasma Wayland when slicing detailed models with NVIDIA GPU
  • #11723: preview completely broken when launching normally on Linux with NVIDIA GPU
  • #6433: Wayland, no 3D view after NVIDIA driver update
  • #8372: feature request to use zink for better Wayland support on NVIDIA
  • #6900: 3D preview blank on Wayland with latest NVIDIA drivers
  • #10059: will not start in Wayland
  • #11698: Mesa/Zink memory allocation error on Wayland + NVIDIA

The practical workaround is to log out, go to your display manager (GDM, SDDM, LightDM, whichever), and pick the X11 or Xorg session before logging back in. On GNOME this is a gear icon next to the password field. On KDE Plasma it’s a dropdown in the corner. Log in to X11, launch OrcaSlicer, everything works. It’s not pretty, and it’s not a fix, but it’s reliable.

If you can’t switch sessions (some immutable distros don’t ship an X11 option anymore), you can try launching the AppImage with GDK_BACKEND=x11 prefixed, which forces it through XWayland. Some people report this works, others report it makes things choppier. Mileage genuinely varies. I want to be honest: this is an open compatibility gap, not a solved problem, and anyone who tells you they have a universal fix is selling something. If your GPU is AMD or Intel, none of this applies and Wayland works fine.

For more on what to do when OrcaSlicer outright refuses to launch (which is what this looks like for some users), our guide on what to do when OrcaSlicer won’t open walks through the diagnostic flow.

System requirements that actually matter on Linux

OrcaSlicer’s README doesn’t publish hard RAM or CPU minimums, and I’m not going to invent any. What I can tell you, from running it on machines ranging from a Steam Deck (16 GB RAM, AMD APU) up to a 64 GB Threadripper workstation, is that the slicer is roughly as demanding as PrusaSlicer or Bambu Studio. If you’ve got 8 GB of RAM and a halfway modern GPU, you’ll be fine for most prints. Detailed multi-material slicing or 0.1 mm layer heights on huge plates will chew through RAM.

The things that are verified requirements on Linux:

  • GLIBC 2.38 or newer for the v2.3.1+ AppImage. Use Flatpak if your distro is older.
  • OpenGL 3.3 or newer for the rendering stack. On Linux this is satisfied by Mesa 13+ (Intel and AMD) and any current NVIDIA driver. Practically every GPU made since 2012 supports this.
  • FUSE2 (libfuse2 or libfuse2t64) if you’re running the AppImage.
  • X11 session recommended for NVIDIA proprietary driver users. Wayland works fine on Intel and AMD.

For Windows and macOS install requirements, see our Windows install guide and our macOS install guide. macOS users need Big Sur 11.3 or newer, in case that’s relevant for a dual-boot setup.

Common gotchas and fixes

Most of these I’ve covered above, but here they are in one place so you can ctrl-F to find them later.

“AppImages require FUSE to run”

Install libfuse2 on Ubuntu 22.04, or libfuse2t64 on Ubuntu 24.04+. See the AppImage section above. The canonical AppImage docs (linked earlier) are the reference.

“version `GLIBC_2.38′ not found”

Your distro is older than Ubuntu 24.04 and your host GLIBC is too old. Use the Flatpak instead, or fall back to the v2.3.0 AppImage. Don’t try to upgrade GLIBC system-wide on Debian or Mint, that way lies madness.

“libwebkit2gtk-4.0.so.37: cannot open shared object file”

This is a separate shared-library miss that hit early Ubuntu 24.04 users, documented in Discussion #6318 on the OrcaSlicer GitHub. The new AppImage builds (v2.3.1 and later) generally handle this, but if you do hit it, the cleanest answer is Flatpak.

Pop!_OS specifically can’t open the AppImage

Pop!_OS 22.04 LTS users have hit this combo of FUSE + GLIBC issues, tracked in issue #11516 on the OrcaSlicer GitHub. If you’re on Pop!_OS, install libfuse2 first. If you’re on the older 22.04 LTS branch and the AppImage still refuses, switch to Flatpak.

“Why isn’t there a Snap package?”

There isn’t. OrcaSlicer doesn’t publish an official Snap, and there’s no snapcraft.io listing for it. Use AppImage or Flatpak. Random third-party Snaps in the store are not from the OrcaSlicer team. If you see one, treat it the same way you’d treat an unsigned binary from a forum, which is to say with deep suspicion.

For a broader troubleshooting reference, our OrcaSlicer troubleshooting master guide covers the full diagnostic flow across platforms.

FAQ

Is there an official .deb or .rpm package?

No. The official Linux release assets are AppImage and Flatpak only. There’s no .deb, no .rpm, no official Snap. Anything you find labeled as a “deb for OrcaSlicer” on a third-party site is not coming from the OrcaSlicer team.

Does OrcaSlicer run on a Steam Deck?

Yes, in desktop mode. I run it via Flatpak (the SteamOS Flatpak setup is straightforward, and Flathub is supported). The AppImage also works if you install libfuse2 in the dev mode rootfs, but Flatpak survives system updates without you having to remember to reinstall anything. Flatpak is the right answer on Steam Deck.

Is there an ARM64 (aarch64) Linux build?

Yes, the v2.3.2 release includes OrcaSlicer-Linux-flatpak_V2.3.2_aarch64.flatpak for ARM64 systems. If you’re on a Raspberry Pi 4 or 5 running a 64-bit desktop OS, or some other ARM64 Linux box, you can install via Flathub, which auto-selects the right architecture.

Can I run OrcaSlicer headless from the command line?

OrcaSlicer does have CLI slicing capabilities (inherited from the PrusaSlicer/SuperSlicer lineage), but it’s not the main use case and the docs are sparse. If you need true headless slicing on a print farm, look at the official OrcaSlicer GitHub README’s CLI section. For most people, the GUI is the way.

How do I completely remove OrcaSlicer from my system?

For the AppImage, delete the .AppImage file and remove ~/.config/OrcaSlicer/ if you want to wipe profiles. For Flatpak, run flatpak uninstall com.orcaslicer.OrcaSlicer and optionally flatpak uninstall --unused to clean up the runtime. For AUR, paru -R orca-slicer-bin or whichever package you installed. Each method’s config is at the paths in the profile storage section above.

Is OrcaSlicer free software?

Yes, it’s licensed under AGPL-3.0-only, the same as the AUR orca-slicer source package’s license tag. You can read the source, modify it, redistribute it, all the usual AGPL freedoms apply.

I installed it but it’s not in my application menu

For the AppImage, install AppImageLauncher from your distro’s repos to handle desktop integration. For Flatpak and AUR installs, the .desktop file is created automatically and the app should appear after you log out and back in (or run update-desktop-database ~/.local/share/applications/).

Wrapping up

The honest summary is that Linux installation for OrcaSlicer in 2026 is genuinely simple if you pick the right route for your distro. AppImage for current Ubuntu-family distros, Flatpak for anything older or immutable, AUR for the Arch crowd. The gotchas (FUSE, GLIBC 2.38, NVIDIA + Wayland) are real but well-understood, and every single one has a documented workaround. If you’ve made it this far without a working install, the answer is almost always “use Flatpak.”

Once you’re up and running, head over to the main OrcaSlicer download page for cross-platform reference, or if you want to keep your profiles intact across upgrades, the profile preservation guide is worth bookmarking before your next major version bump. Happy slicing.

Related OrcaSlicer guides

Leave a Comment