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: unit sunshine.service does not exist
Reported by uceraksu · filed Sep 8, 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 package successfully, but then fails with:
Failed to enable unit: Unit sunshine.service does not exist.Because the script (omarchy-install-service-sunshine) has set -e, it aborts immediately at this step. As a result, everything after the systemctl --user enable --now sunshine line never runs:
- The Moonlight UFW firewall rules (LAN + Tailscale) are never opened
- The "Sunshine Admin" web-app shortcut is never installed
- The Hyprland autostart entry is never added
The user is left with Sunshine installed but not reachable from the network and not auto-starting, with only that one error line as feedback.
Why it happens
The currently packaged sunshine (2026.516.143833-4) ships its systemd user unit as:
/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.servicenot sunshine.service. The install script hardcodes the old unit name:
systemctl --user enable --now sunshinewhich no longer resolves.
Steps to reproduce
- On a current Omarchy install, run
omarchy install service sunshine - Package installs fine
- See the
Failed to enable unit: Unit sunshine.service does not exist.error and the script stops; no firewall rules, webapp, or autostart entry are created
Expected
The script enables/starts Sunshine and completes the remaining setup steps (firewall, admin webapp shortcut, autostart).
Suggested fix
Reference the actual shipped unit name (app-dev.lizardbyte.app.Sunshine.service) in omarchy-install-service-sunshine, e.g.:
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.serviceor resolve it dynamically instead of hardcoding, in case the upstream unit name changes again. Worth double-checking omarchy-remove-service-sunshine too — it calls systemctl --user disable --now sunshine, which currently no-ops silently (the failure is swallowed by || true), so uninstall "succeeds" without actually disabling the real unit.
System details
- Omarchy version: 4.0.2-1
- GPU: AMD Radeon RX 9060 XT (Navi 44, amdgpu driver)
- sunshine package version: 2026.516.143833-4
Workaround used
Manually enabling the correct unit name and completing the remaining steps from the script by hand got Sunshine fully working (systemd unit active, firewall rules added, admin webapp and autostart configured).
View raw text
## What happened Running `omarchy install service sunshine` installs the `sunshine` package successfully, but then fails with: ``` Failed to enable unit: Unit sunshine.service does not exist. ``` Because the script (`omarchy-install-service-sunshine`) has `set -e`, it aborts immediately at this step. As a result, everything after the `systemctl --user enable --now sunshine` line never runs: - The Moonlight UFW firewall rules (LAN + Tailscale) are never opened - The "Sunshine Admin" web-app shortcut is never installed - The Hyprland autostart entry is never added The user is left with Sunshine installed but not reachable from the network and not auto-starting, with only that one error line as feedback. ## Why it happens The currently packaged `sunshine` (2026.516.143833-4) ships its systemd user unit as: ``` /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service ``` not `sunshine.service`. The install script hardcodes the old unit name: ```bash systemctl --user enable --now sunshine ``` which no longer resolves. ## Steps to reproduce 1. On a current Omarchy install, run `omarchy install service sunshine` 2. Package installs fine 3. See the `Failed to enable unit: Unit sunshine.service does not exist.` error and the script stops; no firewall rules, webapp, or autostart entry are created ## Expected The script enables/starts Sunshine and completes the remaining setup steps (firewall, admin webapp shortcut, autostart). ## Suggested fix Reference the actual shipped unit name (`app-dev.lizardbyte.app.Sunshine.service`) in `omarchy-install-service-sunshine`, e.g.: ```bash systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service ``` or resolve it dynamically instead of hardcoding, in case the upstream unit name changes again. Worth double-checking `omarchy-remove-service-sunshine` too — it calls `systemctl --user disable --now sunshine`, which currently no-ops silently (the failure is swallowed by `|| true`), so uninstall "succeeds" without actually disabling the real unit. ## System details - Omarchy version: 4.0.2-1 - GPU: AMD Radeon RX 9060 XT (Navi 44, amdgpu driver) - sunshine package version: 2026.516.143833-4 ## Workaround used Manually enabling the correct unit name and completing the remaining steps from the script by hand got Sunshine fully working (systemd unit active, firewall rules added, admin webapp and autostart configured).
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.