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.
video-acceleration.sh silently skips intel-media-driver on Meteor Lake (GPU reports plain 'Intel Graphics'), leaving Sunshine and all VA-API consumers on software encoding
Reported by tilleyjason-commits · filed Oct 1, 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
What happened
install/hardware/intel/video-acceleration.sh silently fails to install a VA-API driver on machines whose integrated GPU reports itself as Intel Graphics rather than HD Graphics / Iris / Xe — most notably Meteor Lake, which is the entire current Omarchy-on-Intel mainstream.
The script's detection regex:
if [[ ${INTEL_GPU,,} =~ (hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake) ]]; then
omarchy-pkg-add intel-media-driver libvpl vpl-gpu-rt
elif [[ ${INTEL_GPU,,} =~ "gma" ]]; then
omarchy-pkg-add libva-intel-driver
fidoes not match 00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Graphics] (rev 08). No branch fires, no package is installed, and the script exits 0 — so the failure is completely silent.
Reproduced on this machine:
$ GPU=$(lspci | grep -iE 'vga|3d|display' | grep -i 'intel')
$ echo "$GPU"
00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Graphics] (rev 08)
$ if [[ ${GPU,,} =~ (hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake) ]]; then echo MATCH; else echo "NO MATCH"; fi
NO MATCHResulting state — /usr/lib/dri/ has no Intel video driver at all:
$ ls /usr/lib/dri/ | grep -Ei 'iHD|radeonsi|iris|nvf'
iris_dri.so
radeonsi_dri.so
radeonsi_drv_video.soWhy this matters
The visible symptom is in Sunshine. omarchy install service sunshine completes (once the unrelated unit-name bug is worked around), Sunshine starts, and logs this:
Info: Trying encoder [vaapi]
Info: Creating encoder [h264_vaapi]
Info: Encoder [vaapi] failed
Info: Found H.264 encoder: libx264 [software]It falls back to CPU encoding, which is not a Sunshine problem — Sunshine is correctly reporting that no VA-API driver exists. On a Meteor Lake the hardware encoder is fully capable of H.264, H.265 and AV1, so this leaves capable hardware idle for software x264.
The same missing driver degrades any other VA-API consumer (screen recording, ffmpeg transcode, hardware-accelerated video playback in Chromium).
Note this is not the same as #7752 / #9048 / #12054, which are about the omarchy/sunshine package being built without CUDA so NVIDIA users lose NVENC. Those are NVIDIA-side. This one is the Intel install script never installing intel-media-driver in the first place.
Steps to reproduce
- On an Omarchy install with a Meteor Lake (or any Intel iGPU enumerating as plain
Intel Graphics) integrated GPU. ls /usr/lib/dri/— noiHD_drv_video.so.omarchy install service sunshine, then check the encoder line in the log as above.
Suggested fix
Match the modern Intel branding more broadly rather than enumerating marketing names, e.g. keying off the PCI device ID / Meteor Lake|Phoenix Lake|Raptor Lake|Alder Lake and defaulting unknown Intel iGPUs to the intel-media-driver branch instead of falling through silently. Failing that, make the fall-through visible so the user is told the driver was skipped.
System details
| Omarchy | 4.0.4-1 |
| Kernel | 7.2.5-3-omarchy |
| GPU | Intel Meteor Lake-P [Intel Graphics] (rev 08), driver i915 |
| Sunshine | omarchy/sunshine 2026.516.143833-4.1 |
| libva | 2.24.1-1 |
intel-media-driver | not installed |
Happy to provide vainfo output after installing the driver manually to confirm the hardware encoder path works once iHD_drv_video.so is present.
View raw text
### What happened
`install/hardware/intel/video-acceleration.sh` silently fails to install a VA-API driver on machines whose integrated GPU reports itself as `Intel Graphics` rather than `HD Graphics` / `Iris` / `Xe` — most notably **Meteor Lake**, which is the entire current Omarchy-on-Intel mainstream.
The script's detection regex:
```bash
if [[ ${INTEL_GPU,,} =~ (hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake) ]]; then
omarchy-pkg-add intel-media-driver libvpl vpl-gpu-rt
elif [[ ${INTEL_GPU,,} =~ "gma" ]]; then
omarchy-pkg-add libva-intel-driver
fi
```
does not match `00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Graphics] (rev 08)`. No branch fires, no package is installed, and the script exits 0 — so the failure is completely silent.
Reproduced on this machine:
```
$ GPU=$(lspci | grep -iE 'vga|3d|display' | grep -i 'intel')
$ echo "$GPU"
00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Graphics] (rev 08)
$ if [[ ${GPU,,} =~ (hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake) ]]; then echo MATCH; else echo "NO MATCH"; fi
NO MATCH
```
Resulting state — `/usr/lib/dri/` has no Intel video driver at all:
```
$ ls /usr/lib/dri/ | grep -Ei 'iHD|radeonsi|iris|nvf'
iris_dri.so
radeonsi_dri.so
radeonsi_drv_video.so
```
### Why this matters
The visible symptom is in Sunshine. `omarchy install service sunshine` completes (once the unrelated unit-name bug is worked around), Sunshine starts, and logs this:
```
Info: Trying encoder [vaapi]
Info: Creating encoder [h264_vaapi]
Info: Encoder [vaapi] failed
Info: Found H.264 encoder: libx264 [software]
```
It falls back to CPU encoding, which is not a Sunshine problem — Sunshine is correctly reporting that no VA-API driver exists. On a Meteor Lake the hardware encoder is fully capable of H.264, H.265 and AV1, so this leaves capable hardware idle for software x264.
The same missing driver degrades any other VA-API consumer (screen recording, `ffmpeg` transcode, hardware-accelerated video playback in Chromium).
Note this is *not* the same as #7752 / #9048 / #12054, which are about the `omarchy/sunshine` package being built without CUDA so NVIDIA users lose NVENC. Those are NVIDIA-side. This one is the Intel install script never installing `intel-media-driver` in the first place.
### Steps to reproduce
1. On an Omarchy install with a Meteor Lake (or any Intel iGPU enumerating as plain `Intel Graphics`) integrated GPU.
2. `ls /usr/lib/dri/` — no `iHD_drv_video.so`.
3. `omarchy install service sunshine`, then check the encoder line in the log as above.
### Suggested fix
Match the modern Intel branding more broadly rather than enumerating marketing names, e.g. keying off the PCI device ID / `Meteor Lake|Phoenix Lake|Raptor Lake|Alder Lake` and defaulting unknown Intel iGPUs to the `intel-media-driver` branch instead of falling through silently. Failing that, make the fall-through visible so the user is told the driver was skipped.
### System details
| | |
|---|---|
| Omarchy | 4.0.4-1 |
| Kernel | 7.2.5-3-omarchy |
| GPU | Intel Meteor Lake-P [Intel Graphics] (rev 08), driver `i915` |
| Sunshine | omarchy/sunshine 2026.516.143833-4.1 |
| libva | 2.24.1-1 |
| `intel-media-driver` | not installed |
Happy to provide `vainfo` output after installing the driver manually to confirm the hardware encoder path works once `iHD_drv_video.so` is present.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 20:31 UTC