Skip to main content
Version: Stable

Bazzite

Beta

Bazzite is a beta platform: Core installs and runs, but some launchers and setup paths are still being completed.

Zaparoo Core on Bazzite supports launching games from Steam, Lutris, Heroic, standalone emulators, EmuDeck, RetroDECK, Bottles, Faugus, and Moonlight, plus shell scripts. Release builds are available for both AMD64 and ARM64 architectures.

File paths​

ItemPath
Config file~/.config/zaparoo/config.toml
Data directory~/.local/share/zaparoo
Log file/tmp/<session_id>-zaparoo/core.log
Mappings directory~/.local/share/zaparoo/mappings

Where ~ is the home directory of the current user.

Install​

Open a terminal and run:

curl -fsSL https://zaparoo.org/install.sh | bash

This installs all necessary components and sets up the service to run on startup. Since Bazzite has an immutable root filesystem, the installation is user-local (installed to ~/.local/bin). After installation, Core checks for new releases and can update itself in place; see Core updates.

Once Core is running, write your first token from the Zaparoo App or the built-in web UI at http://127.0.0.1:7497/app/.

Uninstall​

Remove the installed components, leaving the application binary until last:

~/.local/bin/zaparoo -uninstall service
~/.local/bin/zaparoo -uninstall desktop
sudo ~/.local/bin/zaparoo -uninstall hardware
~/.local/bin/zaparoo -uninstall application

Client security​

Encryption is off by default on Bazzite, so the Zaparoo App and browsers connect without pairing. To require pairing with a PIN, set encryption = true in config.toml; Core then shows the PIN under Settings > Clients > Pair in the terminal UI or with ~/.local/bin/zaparoo -pair.

Readers​

Launchers​

LauncherSystemsNotes
SteamPCNative and Flatpak Steam installations
LutrisPCNative or Flatpak library data
HeroicPCEpic Games and GOG titles
Standalone emulatorsMultipleInstalled native, AppImage, or Flatpak emulators
EmuDeckMultipleSystems from an EmuDeck installation
RetroDECKMultipleSystems from a RetroDECK installation
BottlesPCPrograms from Bottles
FaugusPCGames from Faugus Launcher
MoonlightPCStreamed apps through Moonlight
KodiMediaVideos, movies, TV shows, music
Web BrowserN/AOpens URLs in default browser
Shell ScriptsAnyCustom .sh file execution

Steam​

Launches games from your Steam library. Both native (pre-installed) and Flatpak Steam installations are automatically detected. Games are launched using xdg-open, which works in both desktop and gaming modes.

Games are indexed from:

  • ~/.steam/steam/steamapps/
  • ~/.local/share/Steam/

To manually launch a Steam game, write steam://<app_id> to a token.

Lutris and Heroic​

Core indexes installed PC games from Lutris and Heroic during a media database update. It checks native and Flatpak library locations. Lutris comes with Bazzite; Heroic is available from Bazaar.

Run each launcher at least once and install its games before updating the media database. Core reads:

  • Lutris installed games from pga.db and launches them with lutris:// entries.
  • Heroic installed Epic Games and GOG titles from its library files and launches them with heroic:// entries.

Emulators​

Core registers launchers for emulators it finds installed, whether native, AppImage, or Flatpak, and adds EmuDeck and RetroDECK systems when either is installed. Detection rules, supported systems, file types, and pointer files are listed under standalone emulators, EmuDeck, and RetroDECK on the Linux launchers page. Use launchers.preference to choose between the Native, EmuDeck, and RetroDECK groups.

Bottles, Faugus, and Moonlight​

Programs from Bottles, games from Faugus Launcher, and streamed apps through Moonlight are indexed and launched the same way as on desktop Linux.

Gaming Mode​

Core manages gamescope focus for non-Steam launchers in Gaming Mode, including Kodi, scripts, and custom launchers. It restores the previous focus state after the launched window closes. Return to Menu stops the active launcher; Steam's Game Mode shell remains responsible for displaying its menu.

Kodi​

Launch media content from a Kodi instance running on your network.

Supported content:

  • Video and audio files
  • Movies and TV episodes
  • Music (songs, albums, artists)
config.toml
[[launchers.default]]
launcher = "Kodi"
server_url = "http://kodi:8080"

Replace kodi:8080 with your Kodi instance's address and web interface port.

Shell scripts​

Execute arbitrary shell scripts. Requires explicit allow list configuration for security.

config.toml
[launchers]
allow_file = [
"^/home/.*/scripts/.*\\.sh$"
]