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 aborts: enables non-existent sunshine.service unit
Reported by rkondratowicz · filed Sep 21, 2026Closed upstream on 2026-09-21 by its own reporter rkondratowicz, as a duplicate of #12499 (R-330). GitHub close reason: duplicate.
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
omarchy install service sunshine fails partway through and exits early.
The script (/usr/share/omarchy/bin/omarchy-install-service-sunshine, line 74) runs:
systemctl --user enable --now sunshineBut the sunshine package it installs (omarchy-pkg-add sunshine) does not provide a unit named sunshine.service. It ships:
/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.serviceThat unit only declares Alias=sunshine.service in its [Install] section, so sunshine.service is not resolvable until the real unit has been enabled once. The enable therefore fails:
Failed to enable unit: Unit sunshine.service does not existBecause the script begins with set -e, it aborts on this line and skips everything after it: opening the UFW ports, installing the Sunshine Admin webapp, and adding the Hyprland autostart entry. The user is left with Sunshine installed but not enabled, no firewall rules, no web UI shortcut, and no autostart.
What was expected
omarchy install service sunshine should complete end to end on a fresh system.
Steps to reproduce
- On a system where
sunshineis not yet installed andsunshine.servicehas never been enabled, run:
omarchy install service sunshine- Observe it stop at
systemctl --user enable --now sunshinewithUnit sunshine.service does not exist.
Suggested fix
Enable the package's real unit name (or an alias that actually resolves). For example:
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.serviceOptionally the UFW/webapp/autostart steps could run before this line, or the enable could tolerate either unit name, so a future rename doesn't abort the whole installer.
Workaround I used
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.serviceThen manually opened the Sunshine ports with ufw, installed the Sunshine Admin webapp, and added o.launch_on_start("sunshine") to ~/.config/hypr/autostart.lua.
System details
- Omarchy: 4.0.4-1 (stable channel)
- Kernel: 7.2.5-3-omarchy
- CPU/GPU: AMD Ryzen 9 7940HS / Radeon 780M
sunshinepackage: 2026.516.143833-4.1
Note: omarchy debug --no-sudo --print, referenced in the contributing guide, does not exist in this version (reports "Unknown Omarchy command").
View raw text
## What happened
`omarchy install service sunshine` fails partway through and exits early.
The script (`/usr/share/omarchy/bin/omarchy-install-service-sunshine`, line 74) runs:
```bash
systemctl --user enable --now sunshine
```
But the `sunshine` package it installs (`omarchy-pkg-add sunshine`) does not provide a unit named `sunshine.service`. It ships:
```
/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
```
That unit only declares `Alias=sunshine.service` in its `[Install]` section, so `sunshine.service` is not resolvable until the real unit has been enabled once. The enable therefore fails:
```
Failed to enable unit: Unit sunshine.service does not exist
```
Because the script begins with `set -e`, it aborts on this line and skips everything after it: opening the UFW ports, installing the Sunshine Admin webapp, and adding the Hyprland autostart entry. The user is left with Sunshine installed but not enabled, no firewall rules, no web UI shortcut, and no autostart.
## What was expected
`omarchy install service sunshine` should complete end to end on a fresh system.
## Steps to reproduce
1. On a system where `sunshine` is not yet installed and `sunshine.service` has never been enabled, run:
```bash
omarchy install service sunshine
```
2. Observe it stop at `systemctl --user enable --now sunshine` with `Unit sunshine.service does not exist`.
## Suggested fix
Enable the package's real unit name (or an alias that actually resolves). For example:
```bash
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
```
Optionally the UFW/webapp/autostart steps could run before this line, or the enable could tolerate either unit name, so a future rename doesn't abort the whole installer.
## Workaround I used
```bash
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
```
Then manually opened the Sunshine ports with `ufw`, installed the Sunshine Admin webapp, and added `o.launch_on_start("sunshine")` to `~/.config/hypr/autostart.lua`.
## System details
- Omarchy: 4.0.4-1 (stable channel)
- Kernel: 7.2.5-3-omarchy
- CPU/GPU: AMD Ryzen 9 7940HS / Radeon 780M
- `sunshine` package: 2026.516.143833-4.1
Note: `omarchy debug --no-sudo --print`, referenced in the contributing guide, does not exist in this version (reports "Unknown Omarchy command").
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.