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.
nvidia.lua sets LIBVA_DRIVER_NAME=nvidia on hybrid Intel+NVIDIA laptops; Brave/Chromium video playback stalls the GPU process
Reported by ferriskleier · filed Aug 30, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #8215 (R-1472). GitHub close reason: completed.
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
What happened
On a hybrid Intel + NVIDIA laptop, default/hypr/nvidia.lua sets LIBVA_DRIVER_NAME=nvidia whenever a GSP-capable NVIDIA GPU is present. The Intel iGPU is the render device for Hyprland and the browser. Chromium-based browsers (Brave 1.94, Chromium 151) then send VA-API video decode to the NVIDIA GPU while rendering on Intel.
Since the 2026-08-29 update this path stalls the browser GPU process on any page that plays video (gronkh.tv, x.com timeline with autoplay):
- audio plays, the video frame stays frozen on the poster image
- the URL bar stops repainting (typed text is invisible until navigation)
- the page recovers as soon as you navigate away
No crash, nothing in journalctl or dmesg (no GPU hang or reset).
What was expected
Video plays with hardware decode on the GPU that renders the session (Intel iHD).
Ruled out (by downgrade tests, each with a fresh browser profile)
| Test | Result |
|---|---|
| mesa 26.2.1 → 26.1.7 | still broken |
| brave-bin 1.94.117 → 1.93.136 | still broken |
| fresh profile, no flags | still broken |
--disable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL (CPU decode) | works, but Google Maps and WebGL get laggy |
LIBVA_DRIVER_NAME=iHD (Intel decode), no other change | works, full GPU use |
Which package regressed the NVIDIA VA-API path is not established. Candidates from the same update: linux 7.1.8 → 7.1.9 (nvidia-open-dkms 610.57.04 rebuilt), linux-firmware 20260810-1 → -2. libva-nvidia-driver 0.0.17 and nvidia-utils 610.57.04 are unchanged since 2026-08-14 and worked until 2026-08-29.
Workaround
Append to ~/.config/hypr/hyprland.lua (loads after Omarchy defaults):
hl.env("LIBVA_DRIVER_NAME", "iHD")Requires a logout; hyprctl reload does not apply env changes.
Suggestion
On hybrid laptops where the render device is the iGPU (/dev/dri/renderD128 is Intel/AMD), nvidia.lua could leave LIBVA_DRIVER_NAME to the iGPU's driver (iHD for intel-media-driver, radeonsi for AMD) and only set nvidia when the NVIDIA GPU is the primary render device. The Intel decode path is also the more robust one for browsers on Wayland.
Side note found on the way: the interrupted omarchy-update (killed during 90-mkinitcpio-install) left the old kernel in the UKI; pacman -S linux repaired it. Not related to this report, mentioned only because it made the first diagnosis harder.
System
- omarchy 4.0.1-1, hyprland 0.56.2-1, linux 7.1.9.arch1-2
- ThinkPad P14s Gen 4: Intel Raptor Lake-P Iris Xe (render device) + NVIDIA RTX A500 Laptop GPU (GA107GLM)
- nvidia-open-dkms / nvidia-utils 610.57.04-1, libva-nvidia-driver 0.0.17-1, intel-media-driver 26.2.4-1, mesa 26.2.1-1
- brave-bin 1.94.117-1 and chromium 151.0.7922.173-1 both affected
Filed by Claude Fable 5 via Claude Code.
View raw text
## What happened
On a hybrid Intel + NVIDIA laptop, `default/hypr/nvidia.lua` sets `LIBVA_DRIVER_NAME=nvidia` whenever a GSP-capable NVIDIA GPU is present. The Intel iGPU is the render device for Hyprland and the browser. Chromium-based browsers (Brave 1.94, Chromium 151) then send VA-API video decode to the NVIDIA GPU while rendering on Intel.
Since the 2026-08-29 update this path stalls the browser GPU process on any page that plays video (gronkh.tv, x.com timeline with autoplay):
- audio plays, the video frame stays frozen on the poster image
- the URL bar stops repainting (typed text is invisible until navigation)
- the page recovers as soon as you navigate away
No crash, nothing in `journalctl` or `dmesg` (no GPU hang or reset).
## What was expected
Video plays with hardware decode on the GPU that renders the session (Intel iHD).
## Ruled out (by downgrade tests, each with a fresh browser profile)
| Test | Result |
| --- | --- |
| mesa 26.2.1 → 26.1.7 | still broken |
| brave-bin 1.94.117 → 1.93.136 | still broken |
| fresh profile, no flags | still broken |
| `--disable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL` (CPU decode) | works, but Google Maps and WebGL get laggy |
| `LIBVA_DRIVER_NAME=iHD` (Intel decode), no other change | works, full GPU use |
Which package regressed the NVIDIA VA-API path is not established. Candidates from the same update: linux 7.1.8 → 7.1.9 (nvidia-open-dkms 610.57.04 rebuilt), linux-firmware 20260810-1 → -2. `libva-nvidia-driver` 0.0.17 and `nvidia-utils` 610.57.04 are unchanged since 2026-08-14 and worked until 2026-08-29.
## Workaround
Append to `~/.config/hypr/hyprland.lua` (loads after Omarchy defaults):
```lua
hl.env("LIBVA_DRIVER_NAME", "iHD")
```
Requires a logout; `hyprctl reload` does not apply env changes.
## Suggestion
On hybrid laptops where the render device is the iGPU (`/dev/dri/renderD128` is Intel/AMD), `nvidia.lua` could leave `LIBVA_DRIVER_NAME` to the iGPU's driver (`iHD` for intel-media-driver, `radeonsi` for AMD) and only set `nvidia` when the NVIDIA GPU is the primary render device. The Intel decode path is also the more robust one for browsers on Wayland.
Side note found on the way: the interrupted `omarchy-update` (killed during `90-mkinitcpio-install`) left the old kernel in the UKI; `pacman -S linux` repaired it. Not related to this report, mentioned only because it made the first diagnosis harder.
## System
- omarchy 4.0.1-1, hyprland 0.56.2-1, linux 7.1.9.arch1-2
- ThinkPad P14s Gen 4: Intel Raptor Lake-P Iris Xe (render device) + NVIDIA RTX A500 Laptop GPU (GA107GLM)
- nvidia-open-dkms / nvidia-utils 610.57.04-1, libva-nvidia-driver 0.0.17-1, intel-media-driver 26.2.4-1, mesa 26.2.1-1
- brave-bin 1.94.117-1 and chromium 151.0.7922.173-1 both affected
Filed by Claude Fable 5 via Claude Code.
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.