Faugus Launcher: a GTK4 front end for UMU-Launcher on Linux

What Faugus Launcher is, and who it is for

Faugus Launcher describes itself as "a simple and lightweight app for running Windows games using UMU-Launcher". That single sentence sets the boundary. It is not a compatibility layer, and it does not ship Wine. UMU-Launcher does the runtime work, and Faugus is the graphical layer that stores your game entries, launches them and shows them as a list, grid or cover wall.

The audience is a Linux user who already has a working Proton or UMU setup and is tired of editing launch commands by hand. The README points at a default prefix location of ~/Faugus/ and a Proton location of ~/.local/share/Steam/compatibilitytools.d/, so the intended user is someone who has Steam installed, or at least has Proton builds dropped in the standard compatibility tools directory. If you have neither, the app has nothing to point at.

It is a poor fit for anyone expecting a storefront. There is no catalogue, no download of game files, no account system. You bring the game, usually a Windows installer or an already installed directory, and Faugus records how to start it. That is the whole product.

The UMU-Launcher dependency is the architecture

The repository layout tells most of the story: a faugus/ Python package, a data/ directory, a languages/ directory for translations, assets/ for icons and images, plus meson.build and meson_options.txt for the build. The entry point is the faugus-launcher script at the top level. There is no Wine source tree, no bundled runtime, no patched Proton.

That means the data flow is short. Faugus keeps its own configuration and per-game entries, resolves a Proton or UMU runtime from the compatibility tools path, and hands the launch off to UMU-Launcher. Everything that can go wrong with Wine, DXVK, Vulkan or a game's own DRM happens below Faugus, in code the project does not own. When a game fails, the useful log is usually UMU's, not Faugus's.

The dependency list in the README confirms the scope: meson, ninja, pygobject, requests, pillow, vdf, psutil, dbus-python, icoextract, gtk4, libadwaita and libmanette. vdf is there to read Steam's own metadata files, icoextract to pull icons out of Windows executables, dbus-python for desktop integration, and libmanette for the gamepad mapping table the README publishes. This is a desktop application that reads other tools' data, not a runtime.

Two locations in the README are worth noting because they are effectively configuration contracts. Prefixes default to ~/Faugus/, and Proton builds are expected under ~/.local/share/Steam/compatibilitytools.d/. Move either and you are relying on behaviour the README does not describe.

Installing Faugus Launcher and adding a first game

Every install path in the README is distro-specific, so pick the one that matches your system. On Arch-based distributions, including the CachyOS and Manjaro users who search for this, the AUR package is the shortest route.

yay -S --noconfirm faugus-launcher

The README gives this as the AUR command with the --noconfirm flag included, so the build runs without prompts. On Fedora and Nobara, the project publishes a Copr repository instead.

sudo dnf -y copr enable faugus/faugus-launcher
sudo dnf -y install faugus-launcher

Ubuntu, Mint and KDE Neon users get a PPA. Note the i386 architecture line: it is the first command in the README's PPA block, and skipping it is a common way to end up with a half-installed Wine stack.

sudo dpkg --add-architecture i386
sudo add-apt-repository -y ppa:faugus/faugus-launcher
sudo apt update
sudo apt install -y faugus-launcher

If you would rather not add a repository, the README also documents a direct .deb download. The version in the URL is pinned to 2.2.0, so this command installs that release and not whatever is newest.

sudo dpkg --add-architecture i386
sudo apt update
sudo apt install -y wget
mkdir -p ~/faugus-launcher
wget -P ~/faugus-launcher https://github.com/Faugus/faugus-launcher/releases/download/2.2.0/faugus-launcher_2.2.0-1_all.deb
sudo apt install -y ~/faugus-launcher/*.deb
sudo rm -r ~/faugus-launcher

Flatpak is the most portable option and the one to use on a Steam Deck or an immutable distribution. The README gives the install and the run command separately, plus a MangoHud layer for the Flatpak runtime.

flatpak install flathub io.github.Faugus.faugus-launcher
flatpak run io.github.Faugus.faugus-launcher
flatpak install org.freedesktop.Platform.VulkanLayer.MangoHud/x86_64/25.08

The Flatpak build needs explicit permissions, and this is where most first-run confusion comes from. Without the filesystem override, the sandbox cannot read Steam's data directory, so Steam users and games will not appear. Without the two talk-name overrides, Steam and Faugus cannot ask each other to launch shortcuts.

sudo flatpak override io.github.Faugus.faugus-launcher --filesystem=~/.var/app/com.valvesoftware.Steam/
sudo flatpak override io.github.Faugus.faugus-launcher --talk-name=org.freedesktop.Flatpak
sudo flatpak override com.valvesoftware.Steam --talk-name=org.freedesktop.Flatpak

Building from source follows the standard Meson flow, and the README lists the dependencies in one line.

meson setup builddir --prefix=/usr
cd builddir
ninja
sudo ninja install

Once it starts, the first real use is adding an entry. The README's gamepad table shows an Add game/app action bound to L1 on a PlayStation pad and LB on an Xbox pad, with Settings on R1 or RB. On a keyboard you go through the same Add game/app dialog, point it at the game's executable or installer, and let it create a prefix under ~/Faugus/. The README does not walk through that dialog, so expect to learn it from the interface rather than the documentation.

Where the documentation runs out

The README is an installation document, not a manual. It has no usage section beyond an embedded YouTube link, which means the add-game dialog, prefix options, environment variable handling and per-game overrides are undocumented in the repository. If you need to know which variables Faugus passes to UMU, or whether it supports a custom WINEPREFIX per entry, the README is silent.

There is also no rollback story. Nothing in the README describes downgrading, exporting your game list, or what happens to entries if you switch between the native package and the Flatpak build. Those two installs keep separate data: the Flatpak override path in the README points at ~/.var/app/io.github.Faugus.faugus-launcher/config/faugus-launcher/, while a native install would use the normal XDG config location. Switching between them means your library does not follow you.

The wrong-tool case is broader. If your games come from Steam, Heroic or Lutris with existing libraries and cloud saves, Faugus does not import them wholesale; it reads Steam's local files for detection, per the vdf dependency, but it is not a library manager for other stores. If a game needs a scripted installer, a specific Wine version, or heavy per-game registry work, a launcher that hands off to UMU with a GUI is not where you want to be doing that. And if you are on a distribution where none of the five install channels apply, you are building from source against a dependency list that includes gtk4, libadwaita and icoextract.

Faugus Launcher versus Lutris, Heroic and Bottles

The comparison people search for is Faugus against Lutris. The difference is scope, not quality. Lutris is a runner framework: it maintains scripts for hundreds of games, manages multiple Wine and emulator versions, and handles installation recipes. Faugus does none of that. It stores an entry, resolves a Proton build from ~/.local/share/Steam/compatibilitytools.d/, and calls UMU-Launcher. If a game has a Lutris install script, Lutris will do work Faugus will not.

Heroic is a different shape again: it is a client for Epic, GOG and Amazon libraries, with authentication and download management. Faugus has no store integration at all. If your games live in those stores, Heroic addresses the problem Faugus does not.

Bottles is the closest in spirit. It builds and manages Wine prefixes as first-class objects, with versioned bottles, dependency installers and per-bottle configuration. Faugus keeps prefixes under ~/Faugus/ and targets UMU-Launcher specifically. Bottles gives you more control over the prefix; Faugus gives you less to configure and a gamepad-navigable interface.

The honest framing: Faugus is the smallest of the four by design, and that is the trade. You get a GTK4 and libadwaita interface with grid, cover and SteamGridDB views, gamepad mapping and a Proton manager, and you give up install recipes, store clients and deep prefix tooling. The README also lists a Proton Manager among the screenshots, so Proton handling is in scope, but the README does not document what that manager does beyond its name.

Maintenance, licence and the cost of upgrading

The repository is not archived, and the last push was on 2026-08-27, which is the same timestamp as the 2.2.0 release. Releases 2.1.0 on 2026-08-13 and 2.0.6 on 2026-08-05 sit shortly before it, so the current cadence is a release roughly every two to three weeks. That is a real signal about how fast the project moves, and it cuts both ways: fixes arrive quickly, and so do changes you did not ask for.

The practical upgrade cost depends on the channel. AUR, Copr and PPA users get whatever the packager publishes, so a major version can land on an ordinary system update. Flatpak users are pinned to the Flathub build and its runtime. The .deb route is manual, and the README's own example points at 2.2.0, so it will not move until you change the URL. Across all of them, the README does not describe a migration path between major versions, and the jump from 2.0.6 to 2.2.0 in under a month suggests configuration formats are still settling.

The licence is MIT. In plain terms, that is permissive: you can use, modify and redistribute the code, including in modified form, provided the copyright notice and licence text travel with it. The repository carries a LICENSE file at the top level. Nothing here is legal advice, and the only licence document that matters is the one in the repository and the terms of the runtime components Faugus calls, which are separate projects with their own licences.

Editorial conclusion

Adopt Faugus Launcher if you already run UMU-Launcher or Proton-GE and want a graphical library on top of it, and you are willing to install it from a distro-specific channel. Skip it if you need a storefront, per-game scripted installers or a Windows-native client, because the README documents none of those. Before committing, verify two things on your own machine: that Proton builds are present in ~/.local/share/Steam/compatibilitytools.d/, since that is where the README says Faugus looks for them, and that your Flatpak overrides are in place if you use the Flathub build, because without the Steam filesystem override the launcher cannot see Steam users or games.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes