Proof Portal

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-817GitHub issuePublicDecided· Out of scope

Update sunshine package to v2026.906.222525 (security fixes + Linux/NVENC/Wayland improvements)

Reported by dansaiko · filed Sep 8, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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

Update sunshine package to v2026.906.222525 (security fixes + Linux/NVENC/Wayland improvements)revision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

The sunshine package shipped in the Omarchy repo is currently pinned at 2026.516.143833-4, while upstream LizardByte/Sunshine has released v2026.906.222525. Sunshine's own web UI already flags this as available.

On the current packaged version, NVENC hardware encoding fails to initialize on an NVIDIA + Wayland (Hyprland) setup with:

Error: Couldn't scale frame: Invalid argument
Info: Encoder [nvenc] failed

Sunshine falls back to software (libx264) encoding, which is noticeably softer and far more CPU-intensive than hardware encoding.

Why this matters

  • Upstream's v2026.906.222525 release notes state it contains critical security updates and urge users to update.
  • The same release includes "Major Wayland and PipeWire improvements" (DMA-BUF modifier support, display switching, compositor compatibility) and NVIDIA CUDA/CUDA-GL capture path fixes for YUV 4:4:4/HDR encoding — these touch the same code path behind the Couldn't scale frame error above, so this update may also fix that regression.
  • No existing open issue/PR in this repo currently tracks a sunshine version bump.

Note for maintainers

Upstream also flags: "Linux KMS display indices may be reordered — configurations using a numeric output_name may need to reselect their display." Omarchy's default sunshine config may need review when bumping, if anything relies on numeric KMS indices.

Steps to reproduce (NVENC issue)

  1. Install sunshine via omarchy install service sunshine on a system with an NVIDIA GPU under Hyprland.
  2. Connect via Moonlight.
  3. Check ~/.config/sunshine/sunshine.log — NVENC probe fails with Couldn't scale frame: Invalid argument, falls back to software encoding.

System details

  • Omarchy: 4.0.2-1
  • Kernel: 7.1.9-arch1-2
  • CPU: AMD Ryzen 7 3700X 8-Core Processor
  • GPU: NVIDIA GeForce RTX 4070 SUPER
  • NVIDIA driver: nvidia-open-dkms / nvidia-utils 610.57.04-1
  • sunshine (installed): 2026.516.143833-4
  • sunshine (upstream latest): 2026.906.222525

Expected

Omarchy's sunshine package tracks upstream releases reasonably promptly, especially for security-flagged releases.

Reference: https://github.com/LizardByte/Sunshine/releases/tag/v2026.906.222525

View raw text
## What happened
The `sunshine` package shipped in the Omarchy repo is currently pinned at `2026.516.143833-4`, while upstream LizardByte/Sunshine has released `v2026.906.222525`. Sunshine's own web UI already flags this as available.

On the current packaged version, NVENC hardware encoding fails to initialize on an NVIDIA + Wayland (Hyprland) setup with:
```
Error: Couldn't scale frame: Invalid argument
Info: Encoder [nvenc] failed
```
Sunshine falls back to software (libx264) encoding, which is noticeably softer and far more CPU-intensive than hardware encoding.

## Why this matters
- Upstream's `v2026.906.222525` release notes state it **contains critical security updates** and urge users to update.
- The same release includes "Major Wayland and PipeWire improvements" (DMA-BUF modifier support, display switching, compositor compatibility) and NVIDIA CUDA/CUDA-GL capture path fixes for YUV 4:4:4/HDR encoding — these touch the same code path behind the `Couldn't scale frame` error above, so this update may also fix that regression.
- No existing open issue/PR in this repo currently tracks a sunshine version bump.

## Note for maintainers
Upstream also flags: "Linux KMS display indices may be reordered — configurations using a numeric `output_name` may need to reselect their display." Omarchy's default sunshine config may need review when bumping, if anything relies on numeric KMS indices.

## Steps to reproduce (NVENC issue)
1. Install sunshine via `omarchy install service sunshine` on a system with an NVIDIA GPU under Hyprland.
2. Connect via Moonlight.
3. Check `~/.config/sunshine/sunshine.log` — NVENC probe fails with `Couldn't scale frame: Invalid argument`, falls back to software encoding.

## System details
- Omarchy: 4.0.2-1
- Kernel: 7.1.9-arch1-2
- CPU: AMD Ryzen 7 3700X 8-Core Processor
- GPU: NVIDIA GeForce RTX 4070 SUPER
- NVIDIA driver: nvidia-open-dkms / nvidia-utils 610.57.04-1
- sunshine (installed): 2026.516.143833-4
- sunshine (upstream latest): 2026.906.222525

## Expected
Omarchy's sunshine package tracks upstream releases reasonably promptly, especially for security-flagged releases.

Reference: https://github.com/LizardByte/Sunshine/releases/tag/v2026.906.222525

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 11:11 UTC