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 trinknx · filed Sep 16, 2026Closed upstream on 2026-10-12 by the bot omarchybot, as a duplicate (target not recorded).
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Environment
- Omarchy 4.0.4-1, Arch, Hyprland
- Package:
omarchy/sunshine 2026.516.143833-4.1 - GPU: NVIDIA RTX 2080 Ti, driver 610.57.04
What happened
Running omarchy install service sunshine installs the package, then aborts:
Installing Sunshine...
omarchy-pkg-add sunshine
Failed to enable unit: Unit sunshine.service does not exist.The command exits non-zero, and because the script is set -e, every later step never runs: the UFW port rules, the "Sunshine Admin" webapp, and the Hyprland autostart entry are all skipped.
Cause
The package ships the unit as /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service. It declares Alias=sunshine.service, but that alias symlink is only created by enabling the unit under its real name — so on a fresh install systemctl --user enable --now sunshine cannot resolve and fails (chicken-and-egg).
omarchy-setup-security-sshd-style hardcoded name no longer matches upstream packaging; the upstream binary/service renamed to app-dev.lizardbyte.app.Sunshine.service.
Expected
omarchy install service sunshine completes all steps on a fresh install.
Fix suggestion
Use the real unit name:
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service(or discover the unit name from pacman -Ql sunshine | grep '\.service$' to be robust against future renames).
Workaround
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
# then run the remaining steps of the installer manuallyView raw text
## Environment - Omarchy 4.0.4-1, Arch, Hyprland - Package: `omarchy/sunshine 2026.516.143833-4.1` - GPU: NVIDIA RTX 2080 Ti, driver 610.57.04 ## What happened Running `omarchy install service sunshine` installs the package, then aborts: ``` Installing Sunshine... omarchy-pkg-add sunshine Failed to enable unit: Unit sunshine.service does not exist. ``` The command exits non-zero, and because the script is `set -e`, every later step never runs: the UFW port rules, the "Sunshine Admin" webapp, and the Hyprland autostart entry are all skipped. ## Cause The package ships the unit as `/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service`. It declares `Alias=sunshine.service`, but that alias symlink is only created *by* enabling the unit under its real name — so on a fresh install `systemctl --user enable --now sunshine` cannot resolve and fails (chicken-and-egg). `omarchy-setup-security-sshd`-style hardcoded name no longer matches upstream packaging; the upstream binary/service renamed to `app-dev.lizardbyte.app.Sunshine.service`. ## Expected `omarchy install service sunshine` completes all steps on a fresh install. ## Fix suggestion Use the real unit name: ```bash systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service ``` (or discover the unit name from `pacman -Ql sunshine | grep '\.service$'` to be robust against future renames). ## Workaround ```bash systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service # then run the remaining steps of the installer manually ```
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.
- Out of scopeDecided by agents · verified · 2026-10-09 14:07 UTC