Bazzite/Atomic Distro Support and Major Build System Overhaul

[fcaraujo]

Hey I also have a nova pro wireless and running on bazzite so when I got the project found some issues (some already opened) so I decided to give it a go and also fix them without being too much intrusive.

Later I'll add a more comprehensive list of changes here, but opening the PR now so at least you can wrap your head around and consider the changes.

Summary: identify if it's running on an atomic distro, avoid the annoying PEP668 errors, fix the service startup issues and customize icon for Hyprland/Waybar users (also identified the current theme so the settings screen) so my tray icon is light (added an optional configuration + the screen is dark themed).

This ended up turning into a full makefile install (improved workflow which replaced the *.sh script, but I didn't change mostly of the dependency management to keep the project as is and up to you if you wanna change later) + adding some dx and trying to make life easier for everyone.

Fully tested on Bazzite with make install and uninstall, also during development you can use make dev so it reinstalls after built.

[stephanboersma]

This is super cool! I am just trying to install this on my fresh bazzite instance.

The install itself went well but the service doesn't run:

● arctis-manager.service - Arctis Manager
     Loaded: loaded (/home/sbo/.local/share/systemd/user/arctis-manager.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: activating (auto-restart) (Result: exit-code) since Sun 2025-11-30 14:22:30 CET; 2s ago
 Invocation: e47c091f15ba443ba65b13b58574f215
    Process: 7368 ExecStartPre=/bin/sh -c echo "Waiting for compositor..."; for i in $(seq 1 60); do if [ -S "${XDG_RUNTIME_DIR}/wayland-0" ] || [ -S >
    Process: 7371 ExecStart=/home/sbo/.local/bin/arctis-manager (code=exited, status=101)
   Main PID: 7371 (code=exited, status=101)
   Mem peak: 232.3M
        CPU: 731ms

Any idea what my problem is here?

[elegos]

Hello @fcaraujo,

I've recently replaced the way the app is being installed, essentially deprecating install.sh, introducing uv instead of pipenv (which was producing too many problems) and installing the app package-wise only.

The current rehaul is available in the develop branch (btw this merge request points to main, but should point to develop, from which new releases are emerged) - it probably needs still some inter-distro code deduplication (essentially the steps of dependencies download and copy to dest dir are still being duplicated, which is never a good choice).

Also the new packaging system preferes python packages dependencies, if available distro-side (for example Fedora's rpm is now down to ~500 KB).

May you please adapt your installation changes, and explain me the key changes from an architectural point of view?

Thanks :)

[rdamron]

This would be huge. +1 this.