Faugus Launcher: A Lightweight Frontend for UMU-Launcher on Linux

What Faugus Launcher Does and Who It Is For

Faugus Launcher is a small Python application that gives you a graphical way to run Windows games on Linux, using UMU-Launcher underneath. UMU-Launcher is a tool that manages Wine and Proton prefixes for individual games, and Faugus wraps it in a GTK4 interface. The README describes it as 'simple and lightweight,' which is an honest summary: there is no mention of cloud saves, game stores, or plugin systems. The target user is someone on a Linux desktop or a Steam Deck who wants to launch a few Windows titles without opening a terminal or editing Wine config files. The gamepad mapping table in the README suggests the interface is designed for controller use, which points directly at handheld and couch setups.

The Architecture: Python, GTK4, and UMU-Launcher

The repository is written in Python and builds with Meson. The dependency list includes pygobject, gtk4, libadwaita, and libmanette, which indicates a GTK4 UI with gamepad input support. The actual game launching is delegated to UMU-Launcher, which is a separate project from Open-Wine-Components. Faugus does not reimplement Wine or Proton; it reads your Steam compatibility tools from ~/.local/share/Steam/compatibilitytools.d/ and stores its own prefixes under ~/Faugus/. That separation is the core design: Faugus is a frontend, not a compatibility layer. The data flow is straightforward: you add a game, Faugus creates a UMU prefix, and when you press launch, it invokes UMU-Launcher with the appropriate environment. The README does not document the exact command line it uses, so the details of that invocation are not public from this material.

Installation Paths: AUR, COPR, PPA, Flatpak, and Source

The README gives five installation routes. Arch users run yay -S faugus-launcher from the AUR. Fedora and Nobara users enable a COPR repository with sudo dnf copr enable faugus/faugus-launcher and then install. Debian-based distributions get a PPA or a direct .deb download; both require adding the i386 architecture first with sudo dpkg --add-architecture i386. Flatpak is also available from Flathub as io.github.Faugus.faugus-launcher. Building from source uses Meson and Ninja: meson setup builddir --prefix=/usr, then ninja, then sudo ninja install. The dependencies for a source build are listed: meson, ninja, pygobject, requests, pillow, vdf, psutil, dbus-python, icoextract, gtk4, libadwaita, and libmanette. That is a modest list for a GUI app, and the fact that it ships as a single .deb file named faugus-launcher_2.2.0-1_all.deb suggests the Python code is packaged without a complex runtime.

Flatpak Permissions: The Hidden Cost of Convenience

The Flatpak version works, but only after you grant several overrides. The README lists commands like sudo flatpak override io.github.Faugus.faugus-launcher --filesystem=~/.var/app/com.valvesoftware.Steam/ and --talk-name=org.freedesktop.Flatpak. You also need to let Steam talk to Flatpak and give Steam filesystem access to Faugus's config directory so icons appear. This is not a one-command install. If you skip these overrides, Faugus cannot see your Steam games, and Steam cannot launch Faugus shortcuts. The theme permissions are also manual: ~/.themes works natively, but Flatpak requires a separate override for xdg-data/themes. This is a real friction point. A native package avoids most of it, but then you lose the sandboxing that Flatpak offers. The trade-off is explicit in the README, which is unusual and honest.

Gamepad Mapping: Designed for Controller Navigation

The README includes a table for gamepad actions. Cross confirms, Circle cancels, Triangle opens the game menu, Square kills the current game, L1 adds a game or app, R1 opens settings, and Options brings up power options. This is a complete controller scheme for a launcher. It tells you that Faugus is not meant to be used with a keyboard and mouse only. The mapping is PlayStation and Xbox specific, with no mention of Switch Pro or generic controllers, though libmanette should handle those at the driver level. The inclusion of a 'Kill' action on Square is notable: it implies that the launcher expects games to hang or misbehave, and you need a quick way to force quit. That is a practical design choice for a tool that wraps Wine, where crashes are not rare.

Themes and Proton Management: What the Interface Covers

The screenshots section lists five views: main window with list, grid, covers, SteamGridDB, and settings, plus an Add/Edit game dialog and a Proton Manager. The README does not show the images, but the labels tell you the feature set. SteamGridDB support means Faugus can fetch cover art from that service, which is a common need for launchers. The Proton Manager likely lets you pick which Proton version from Steam's compatibilitytools.d directory to use. There is no mention of custom Wine builds, DXVK versions, or per-game environment variables in the README. So the configuration surface is shallow. If you need fine-grained control over a specific game's Wine settings, you will not find it here. The themes section in the README confirms that Faugus follows the system GTK theme, with the usual Flatpak restrictions.

Limitations and Wrong Use Cases

Faugus Launcher has a narrow scope, and that is both its strength and its limit. It does not manage non-Steam games outside of UMU-Launcher's capabilities, and it does not provide a game store integration beyond what UMU-Launcher supports. The README mentions no cloud sync, no achievements, no multiplayer overlay, and no game recording. If you rely on those features, this is the wrong tool. Another limitation is that it depends on UMU-Launcher being installed and working. The README links to UMU-Launcher but does not list it as a dependency, which suggests you must install it separately. The Flatpak permissions also assume a specific Steam installation path; if your Steam library is on an external drive or a non-standard location, the overrides will not work without modification. Finally, the project is young: the latest release is 2.2.0 from August 2026, and the previous releases are only weeks apart. That pace means frequent updates, but also that the API and config layout may change.

Alternatives: Lutris and Bottles

The obvious alternatives are Lutris and Bottles, both of which also run Windows games on Linux. Lutris is a full game library manager with install scripts for thousands of titles, cloud sync, and per-game runners. It uses a database of community-provided installers, so you often click once and play. Bottles focuses on managing Wine prefixes per application, with a graphical interface for configuring DLL overrides, environment variables, and runner versions. The difference in approach is that Faugus delegates almost everything to UMU-Launcher and keeps its own interface minimal, while Lutris and Bottles each implement their own prefix management and configuration layers. Faugus is lighter and simpler, but it gives you less control. If you need Lutris's scripted installs or Bottles' per-prefix settings, Faugus will feel thin. If you want a controller-friendly launcher that just works with UMU, Faugus is the more focused choice.

Maintenance and Licensing

The project is MIT licensed, which means you can reuse the code in commercial projects with attribution. The repository is not archived and had a push on the same day as the 2.2.0 release, so it is actively maintained. The release cadence, with three versions in under a month, suggests rapid iteration. However, that also means you should expect breaking changes between minor versions. The Flatpak packaging is maintained separately on Flathub, and the AUR and COPR packages are community or maintainer-driven. Upgrade cost is low for a Python app: you update via your package manager, and the config lives in ~/Faugus/ and ~/.config/faugus-launcher. The main upgrade risk is that UMU-Launcher itself changes its command-line interface, which would require Faugus to adapt. There is no upgrade guide in the README, so you are on your own if a new version changes the prefix layout or the Steam integration.

Editorial conclusion

Adopt Faugus Launcher if you want a minimal, gamepad-driven frontend for UMU-Launcher on Arch, Fedora, or Ubuntu, and you are comfortable with Flatpak overrides or AUR packages. Skip it if you need a full-featured library manager with cloud sync, or if you prefer to configure Proton and Wine manually. Verify first that your distribution is supported, that the Flatpak permissions match your Steam installation path, and that your GPU drivers and Vulkan layers work with UMU-Launcher before committing.

Official sources

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