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.
intel/video-acceleration.sh doesn't match Intel Wildcat Lake GPU, skips installing intel-media-driver
Reported by theswampdawg · filed Sep 15, 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
Description
\/usr/share/omarchy/install/hardware/intel/video-acceleration.sh\ detects the Intel GPU via \lspci\ and only installs \intel-media-driver libvpl vpl-gpu-rt\ if the device string matches:
\\\`
(hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake)
\\\`
On a laptop with an Intel "Wildcat Lake" iGPU, \lspci\ reports:
\\\`
00:02.0 VGA compatible controller: Intel Corporation Wildcat Lake [Intel Graphics] (rev 01)
\\\`
This string doesn't match any pattern in the regex ("Wildcat Lake" contains none of "hd graphics", "uhd graphics", "xe", "iris", "arc", or "panther lake" as substrings), so the script silently skips installing hardware video acceleration on this hardware. The kernel driver in use is \xe\, so this is exactly the class of hardware the script intends to cover.
Effect
No VA-API driver gets installed on fresh Omarchy installs on Wildcat Lake hardware. Symptom: \vainfo\ errors out / hardware video decode doesn't work in browsers, media players, etc. until the packages are installed manually.
Suggested fix
Add \wildcat\ lake\ (and possibly other upcoming Intel codenames) to the regex in \video-acceleration.sh\:
\\\`
(hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake|wildcat\ lake)
\\\`
Environment
- GPU: Intel Corporation Wildcat Lake [Intel Graphics] (rev 01)
- Kernel driver: xe
- Omarchy version: 4.0.3
Manually installing \intel-media-driver libvpl vpl-gpu-rt libva-utils\ fixes hardware video decode (confirmed working via \vainfo\).
View raw text
## Description
\`/usr/share/omarchy/install/hardware/intel/video-acceleration.sh\` detects the Intel GPU via \`lspci\` and only installs \`intel-media-driver libvpl vpl-gpu-rt\` if the device string matches:
\`\`\`
(hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake)
\`\`\`
On a laptop with an Intel "Wildcat Lake" iGPU, \`lspci\` reports:
\`\`\`
00:02.0 VGA compatible controller: Intel Corporation Wildcat Lake [Intel Graphics] (rev 01)
\`\`\`
This string doesn't match any pattern in the regex ("Wildcat Lake" contains none of "hd graphics", "uhd graphics", "xe", "iris", "arc", or "panther lake" as substrings), so the script silently skips installing hardware video acceleration on this hardware. The kernel driver in use is \`xe\`, so this is exactly the class of hardware the script intends to cover.
## Effect
No VA-API driver gets installed on fresh Omarchy installs on Wildcat Lake hardware. Symptom: \`vainfo\` errors out / hardware video decode doesn't work in browsers, media players, etc. until the packages are installed manually.
## Suggested fix
Add \`wildcat\ lake\` (and possibly other upcoming Intel codenames) to the regex in \`video-acceleration.sh\`:
\`\`\`
(hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake|wildcat\ lake)
\`\`\`
## Environment
- GPU: Intel Corporation Wildcat Lake [Intel Graphics] (rev 01)
- Kernel driver: xe
- Omarchy version: 4.0.3
Manually installing \`intel-media-driver libvpl vpl-gpu-rt libva-utils\` fixes hardware video decode (confirmed working via \`vainfo\`).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 13:43 UTC