Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
omarchy-install-service-sunshine fails: enables wrong systemd unit name (sunshine vs app-dev.lizardbyte.app.Sunshine)
Reported by pedro199288 · filed Aug 27, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7050 (R-1810). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What happened
Running omarchy install service sunshine installs the sunshine pacman package successfully, but then fails during setup with an error resembling Failed to enable unit: .... Because the script uses set -e, it aborts at that point — the Moonlight streaming firewall ports are never opened, the "Sunshine Admin" web app launcher is never created, and Hyprland autostart is never configured.
Root cause
/usr/share/omarchy/bin/omarchy-install-service-sunshine runs:
systemctl --user enable --now sunshineBut the sunshine Arch package ships its systemd user unit under the name app-dev.lizardbyte.app.Sunshine.service, not sunshine.service:
$ pacman -Ql sunshine | grep -i service
sunshine /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.serviceSo systemctl --user enable --now sunshine fails with "Unit sunshine.service could not be found." (short name sunshine doesn't resolve as a systemd alias), which trips set -e and halts the rest of the script.
Expected
The script should enable the actual unit name, e.g.:
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service(or resolve the unit name dynamically, in case it changes across Sunshine versions), so the rest of the install (firewall rules, admin web app, autostart entry) completes.
Steps to reproduce
- Fresh Omarchy install without Sunshine.
- Run
omarchy install service sunshine. - Observe pacman install succeeds, but the unit-enable step fails and the script stops before opening firewall ports / installing the admin web app / configuring autostart.
Workaround
Manually enable the correctly-named unit and re-run the rest of the script's logic (firewall rules, omarchy-webapp-install, Hyprland autostart entry) by hand.
System details
- Omarchy version: 4.0.0-1
- Kernel:
7.1.8-arch1-3 - GPU: NVIDIA GeForce RTX 4060 (nvidia driver)
- sunshine package:
2026.516.143833-4
Note
omarchy debug --no-sudo --print does not exist in this Omarchy version (Unknown Omarchy command), so I could not attach the standard diagnostic log.
View raw text
## What happened Running `omarchy install service sunshine` installs the `sunshine` pacman package successfully, but then fails during setup with an error resembling `Failed to enable unit: ...`. Because the script uses `set -e`, it aborts at that point — the Moonlight streaming firewall ports are never opened, the "Sunshine Admin" web app launcher is never created, and Hyprland autostart is never configured. ## Root cause `/usr/share/omarchy/bin/omarchy-install-service-sunshine` runs: ```bash systemctl --user enable --now sunshine ``` But the `sunshine` Arch package ships its systemd user unit under the name `app-dev.lizardbyte.app.Sunshine.service`, not `sunshine.service`: ``` $ pacman -Ql sunshine | grep -i service sunshine /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service ``` So `systemctl --user enable --now sunshine` fails with "Unit sunshine.service could not be found." (short name `sunshine` doesn't resolve as a systemd alias), which trips `set -e` and halts the rest of the script. ## Expected The script should enable the actual unit name, e.g.: ```bash systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service ``` (or resolve the unit name dynamically, in case it changes across Sunshine versions), so the rest of the install (firewall rules, admin web app, autostart entry) completes. ## Steps to reproduce 1. Fresh Omarchy install without Sunshine. 2. Run `omarchy install service sunshine`. 3. Observe pacman install succeeds, but the unit-enable step fails and the script stops before opening firewall ports / installing the admin web app / configuring autostart. ## Workaround Manually enable the correctly-named unit and re-run the rest of the script's logic (firewall rules, `omarchy-webapp-install`, Hyprland autostart entry) by hand. ## System details - Omarchy version: 4.0.0-1 - Kernel: `7.1.8-arch1-3` - GPU: NVIDIA GeForce RTX 4060 (nvidia driver) - sunshine package: `2026.516.143833-4` ## Note `omarchy debug --no-sudo --print` does not exist in this Omarchy version (`Unknown Omarchy command`), so I could not attach the standard diagnostic log.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.