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.
Hybrid Intel+NVIDIA laptops: global LIBVA_DRIVER_NAME=nvidia breaks Chromium video (black YouTube picture)
Reported by lAvArt · filed Oct 1, 2026Closed upstream on 2026-10-02 by its own reporter lAvArt. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
System details
ASUS Vivobook K6602VV — Intel Raptor Lake Iris Xe (i915) + NVIDIA RTX 4060 Laptop (nvidia-open-dkms 610.57.04), Omarchy 4.0.4, kernel 7.2.5-3-omarchy, chromium 152.0.7977.82
What's wrong?
On hybrid Intel + NVIDIA laptops, default/hypr/nvidia.lua sets LIBVA_DRIVER_NAME=nvidia for the whole session when the GPU supports GSP. Chromium renders on the Intel iGPU (its GPU process runs with --render-node-override=/dev/dri/renderD129, the Intel render node), but inherits the NVIDIA VA-API driver from the session environment.
Result: YouTube videos show a black picture and stutter at the start of playback.
Steps to reproduce
1. Install Omarchy on a hybrid Intel iGPU + NVIDIA (GSP-capable) laptop.
2. Open a YouTube video in the default Chromium.
3. Video area stays black / playback stutters at start.
Workaround that fixed it
- Launch Chromium with LIBVA_DRIVER_NAME=iHD (wrapper script + ~/.local/share/applications/chromium.desktop override).
- Add AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,VaapiIgnoreDriverChecks to --enable-features in ~/.config/chromium-flags.conf.
After that, chrome://gpu reports hardware-accelerated video decode and YouTube plays normally.
Possible fix
Don't set LIBVA_DRIVER_NAME=nvidia globally when an Intel/AMD iGPU drives the display (hybrid setups), or set it only for apps that actually run on the NVIDIA GPU.
View raw text
### System details ASUS Vivobook K6602VV — Intel Raptor Lake Iris Xe (i915) + NVIDIA RTX 4060 Laptop (nvidia-open-dkms 610.57.04), Omarchy 4.0.4, kernel 7.2.5-3-omarchy, chromium 152.0.7977.82 ### What's wrong? On hybrid Intel + NVIDIA laptops, `default/hypr/nvidia.lua` sets `LIBVA_DRIVER_NAME=nvidia` for the whole session when the GPU supports GSP. Chromium renders on the Intel iGPU (its GPU process runs with `--render-node-override=/dev/dri/renderD129`, the Intel render node), but inherits the NVIDIA VA-API driver from the session environment. Result: YouTube videos show a black picture and stutter at the start of playback. **Steps to reproduce** 1. Install Omarchy on a hybrid Intel iGPU + NVIDIA (GSP-capable) laptop. 2. Open a YouTube video in the default Chromium. 3. Video area stays black / playback stutters at start. **Workaround that fixed it** - Launch Chromium with `LIBVA_DRIVER_NAME=iHD` (wrapper script + `~/.local/share/applications/chromium.desktop` override). - Add `AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,VaapiIgnoreDriverChecks` to `--enable-features` in `~/.config/chromium-flags.conf`. After that, `chrome://gpu` reports hardware-accelerated video decode and YouTube plays normally. **Possible fix** Don't set `LIBVA_DRIVER_NAME=nvidia` globally when an Intel/AMD iGPU drives the display (hybrid setups), or set it only for apps that actually run on the NVIDIA GPU.
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
- Fixed bypr/9483· confirmed
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.