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/sunshine 2026.516 package: NVENC broken on Turing — falls back to software x264
Reported by trinknx · filed Sep 16, 2026 · open at source
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 (Wayland, wlgrab capture)
- Package:
omarchy/sunshine 2026.516.143833-4.1(omarchy repo) - GPU: NVIDIA RTX 2080 Ti (Turing, sm_75), proprietary driver 610.57.04
- Monitor: single 2560x1440
What happened
Moonlight stream quality is terrible because Sunshine never uses hardware encoding. At startup, encoder probing fails for NVENC and every hardware path, falling back to software libx264:
Info: Trying encoder [nvenc]
Info: Creating encoder [h264_nvenc]
...
Error: Couldn't scale frame: Invalid argument
Info: Encoder [nvenc] failed
Info: Trying encoder [vulkan]
Error: [wlgrab] Could not initialize display with the given hw device type.
Info: Encoder [vulkan] failed
Info: Trying encoder [vaapi]
Error: [h264_vaapi ...] No usable encoding entrypoint found for profile VAProfileH264High (7). # expected: VA-API on NVIDIA is NVDEC-only
Info: Encoder [vaapi] failed
Info: Trying encoder [software]
Info: Found H.264 encoder: libx264 [software]The key line is Couldn't scale frame: Invalid argument — the NVENC encoder is created, then the first-frame CUDA scale fails.
Evidence it's the omarchy build, not the machine
Same machine, same driver, same session:
- System ffmpeg hardware encode works:
$ ffmpeg -f lavfi -i testsrc2=size=2560x1440:rate=60 -t 2 -c:v hevc_nvenc -f null -
# succeeds- Upstream official builds work:
- LizardByte AppImage
2026.914.233613:Found H.264 encoder: h264_nvenc [nvenc],Found HEVC encoder: hevc_nvenc [nvenc], live session encodes withhevc_nvenc. - AUR
sunshine-bin 2026.906.222525-1(official binaries packaged): same result,CLIENT CONNECTEDand the session runshevc_nvenc.
The omarchy repo build is 2026.516 while upstream is at 2026.914, so this is either a build problem in the omarchy package (e.g. bundled CUDA fatbin missing the Turing/sm_75 arch, so the scale kernel fails to launch with EINVAL) or an upstream wlgrab+NVENC bug fixed between 2026.516 and 2026.906.
Expected
NVENC (h264_nvenc / hevc_nvenc) works on Turing with the omarchy-packaged sunshine, as it does with official upstream builds.
Workaround
Install sunshine-bin from the AUR instead:
omarchy pkg aur add sunshine-bin # conflicts with omarchy/sunshine, remove it when prompted
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.serviceHappy to run further diagnostics on the omarchy build if useful (e.g. cuobjdump output from the binary, full startup logs).
View raw text
## Environment - Omarchy 4.0.4-1, Arch, Hyprland (Wayland, wlgrab capture) - Package: `omarchy/sunshine 2026.516.143833-4.1` (omarchy repo) - GPU: NVIDIA RTX 2080 Ti (Turing, sm_75), proprietary driver 610.57.04 - Monitor: single 2560x1440 ## What happened Moonlight stream quality is terrible because Sunshine never uses hardware encoding. At startup, encoder probing fails for NVENC and every hardware path, falling back to software libx264: ``` Info: Trying encoder [nvenc] Info: Creating encoder [h264_nvenc] ... Error: Couldn't scale frame: Invalid argument Info: Encoder [nvenc] failed Info: Trying encoder [vulkan] Error: [wlgrab] Could not initialize display with the given hw device type. Info: Encoder [vulkan] failed Info: Trying encoder [vaapi] Error: [h264_vaapi ...] No usable encoding entrypoint found for profile VAProfileH264High (7). # expected: VA-API on NVIDIA is NVDEC-only Info: Encoder [vaapi] failed Info: Trying encoder [software] Info: Found H.264 encoder: libx264 [software] ``` The key line is `Couldn't scale frame: Invalid argument` — the NVENC encoder is created, then the first-frame CUDA scale fails. ## Evidence it's the omarchy build, not the machine Same machine, same driver, same session: 1. System ffmpeg hardware encode works: ``` $ ffmpeg -f lavfi -i testsrc2=size=2560x1440:rate=60 -t 2 -c:v hevc_nvenc -f null - # succeeds ``` 2. Upstream official builds work: - LizardByte AppImage `2026.914.233613`: `Found H.264 encoder: h264_nvenc [nvenc]`, `Found HEVC encoder: hevc_nvenc [nvenc]`, live session encodes with `hevc_nvenc`. - AUR `sunshine-bin 2026.906.222525-1` (official binaries packaged): same result, `CLIENT CONNECTED` and the session runs `hevc_nvenc`. The omarchy repo build is `2026.516` while upstream is at `2026.914`, so this is either a build problem in the omarchy package (e.g. bundled CUDA fatbin missing the Turing/sm_75 arch, so the scale kernel fails to launch with EINVAL) or an upstream wlgrab+NVENC bug fixed between 2026.516 and 2026.906. ## Expected NVENC (h264_nvenc / hevc_nvenc) works on Turing with the omarchy-packaged sunshine, as it does with official upstream builds. ## Workaround Install `sunshine-bin` from the AUR instead: ```bash omarchy pkg aur add sunshine-bin # conflicts with omarchy/sunshine, remove it when prompted systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service ``` Happy to run further diagnostics on the omarchy build if useful (e.g. `cuobjdump` output from the binary, full startup logs).
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:08 UTC