Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4660GitHub issuePublicReceived

omarchy install service sunshine fails to enable unit on fresh install

Reported by benhadden · filed Aug 23, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7050 (R-1810). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

omarchy install service sunshine fails to enable unit on fresh installrevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

omarchy install service sunshine installs the sunshine package successfully, but then fails with:

Failed to enable unit: Unit sunshine.service does not exist

Because omarchy-install-service-sunshine has set -e, the script aborts right there. Everything after the systemctl --user enable --now sunshine line — opening the Moonlight firewall ports, installing the "Sunshine Admin" webapp, and adding the Hyprland autostart entry — never runs.

Root cause

The Arch sunshine package ships its user systemd unit as:

/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service

with Alias=sunshine.service in its [Install] section. systemd only resolves that alias once the unit has already been enabled by its real name — the alias symlink (~/.config/systemd/user/sunshine.service) doesn't exist yet on a fresh install, so systemctl --user enable --now sunshine fails with "Unit sunshine.service does not exist".

Manually running:

systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service

succeeds, creates the sunshine.service alias symlink, and starts Sunshine correctly. (After that one-time fix, sunshine.service resolves fine going forward.)

Expected behavior

omarchy install service sunshine should enable Sunshine on a fresh install without manual intervention, and should still perform the firewall/webapp/autostart steps afterward.

Suggested fix

In omarchy-install-service-sunshine, enable the service by its canonical unit name instead of the alias:

systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service

Steps to reproduce

  1. Fresh Omarchy system, Sunshine not previously installed.
  2. Run omarchy install service sunshine.
  3. Observe Failed to enable unit: Unit sunshine.service does not exist after package install, and that firewall ports/webapp/autostart are never set up.

System details

  • Omarchy version: 4.0.0-1 (stable channel)
  • Kernel: Linux 7.1.8-arch1-3 x86_64
  • CPU: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
  • GPU: NVIDIA GeForce GTX 970 (GM204)
  • sunshine package version: 2026.516.143833-4-4
View raw text
## What happened

`omarchy install service sunshine` installs the `sunshine` package successfully, but then fails with:

```
Failed to enable unit: Unit sunshine.service does not exist
```

Because `omarchy-install-service-sunshine` has `set -e`, the script aborts right there. Everything after the `systemctl --user enable --now sunshine` line — opening the Moonlight firewall ports, installing the "Sunshine Admin" webapp, and adding the Hyprland autostart entry — never runs.

## Root cause

The Arch `sunshine` package ships its user systemd unit as:

```
/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
```

with `Alias=sunshine.service` in its `[Install]` section. systemd only resolves that alias once the unit has already been enabled by its real name — the alias symlink (`~/.config/systemd/user/sunshine.service`) doesn't exist yet on a fresh install, so `systemctl --user enable --now sunshine` fails with "Unit sunshine.service does not exist".

Manually running:

```bash
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
```

succeeds, creates the `sunshine.service` alias symlink, and starts Sunshine correctly. (After that one-time fix, `sunshine.service` resolves fine going forward.)

## Expected behavior

`omarchy install service sunshine` should enable Sunshine on a fresh install without manual intervention, and should still perform the firewall/webapp/autostart steps afterward.

## Suggested fix

In `omarchy-install-service-sunshine`, enable the service by its canonical unit name instead of the alias:

```bash
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
```

## Steps to reproduce

1. Fresh Omarchy system, Sunshine not previously installed.
2. Run `omarchy install service sunshine`.
3. Observe `Failed to enable unit: Unit sunshine.service does not exist` after package install, and that firewall ports/webapp/autostart are never set up.

## System details

- Omarchy version: 4.0.0-1 (stable channel)
- Kernel: Linux 7.1.8-arch1-3 x86_64
- CPU: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
- GPU: NVIDIA GeForce GTX 970 (GM204)
- sunshine package version: 2026.516.143833-4-4

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.