Bazzite

Beta

Bazzite support is currently in beta. Some features may not work as expected.

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

Item	Path
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.

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

Readers

NFC/RFID

PN532 USB✓Supported

Auto-detected

PN532 Module✓Supported

Depends on wiringUART can auto-detect. I2C is supported.

ACR122U✓Supported

Manual enableUses libnfc: LED and beeper do not work, and some clone variants are incompatible.

RC522!Limited

Via Simple SerialRequires a microcontroller; not a direct USB reader.

Barcode and QR

Zaparoo App camera✓Supported

Via Zaparoo App

RS-232 scanner✓Supported

Manual config

Optical and Media

Optical Drive✓Supported

Manual config

External Drive✓Supported

Manual enable

Custom and Virtual

MQTT Reader✓Supported

Manual config

Simple Serial✓Supported

Manual config

File Reader✓Supported

Manual config

Displays and Integrations

TTY2OLED✓Supported

Manual enable

Launchers

Launcher	Systems	Notes
Steam	PC	Native and Flatpak Steam installations
Lutris	PC	Native or Flatpak library data
Heroic	PC	Epic Games and GOG titles
Standalone emulators	Multiple	Installed native, AppImage, or Flatpak emulators
EmuDeck	Multiple	Systems from an EmuDeck installation
RetroDECK	Multiple	Systems from a RetroDECK installation
Bottles	PC	Programs from Bottles
Faugus	PC	Games from Faugus Launcher
Moonlight	PC	Streamed apps through Moonlight
Kodi	Media	Videos, movies, TV shows, music
Web Browser	N/A	Opens URLs in default browser
Shell Scripts	Any	Custom .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$"
]