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.
mpv wakes the runtime-suspended NVIDIA dGPU on hybrid laptops: ~3.5 s before the first frame (still true with #11690)
Reported by sergihrs · filed Oct 4, 2026 · open at source · 2 revisions
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
System details
- ASUS ROG Zephyrus G16 (GU605CP): Intel Core Ultra 9 285H, Arc 140T iGPU (i915,
boot_vga=1, drives eDP) + RTX 5070 Laptop (nvidia-open 610.57.04,boot_vga=0, runtime-suspended when idle) - Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, mpv 0.41.0-6, mesa/vulkan-intel 26.2.2, vulkan-icd-loader 1.4.357
What's wrong?
Opening any video with Omarchy's default player (mpv, vo=gpu-next on Vulkan) wakes the dGPU: libplacebo enumerates every Vulkan device, the NVIDIA ICD resumes the card, and the first frame appears only after the resume (~3.5 s). The dGPU then stays awake while mpv runs.
This is independent of the VA-API/GLX env: with LIBVA_DRIVER_NAME and __GLX_VENDOR_LIBRARY_NAME unset (what #11690 does on this laptop), it still happens.
Measured on the same 4K60 VP9 file, launched like mpv.desktop, dGPU idle (suspended) before each run:
| env | first frame | dGPU |
|---|---|---|
| Omarchy 4.0.4 default | 3.8–4.0 s | resumed |
LIBVA_DRIVER_NAME/__GLX_VENDOR_LIBRARY_NAME unset (#11690) | 3.7 s | resumed |
+ VK_LOADER_DRIVERS_DISABLE='*nvidia*' | 0.5–0.8 s | stays suspended |
(first frame = mpv's playback restart complete in --log-file; dGPU state from /sys/bus/pci/devices/0000:01:00.0/power/runtime_status.)
Steps to reproduce
- On a hybrid laptop where the iGPU drives the display, let the dGPU suspend (
runtime_status=suspended). - Open a video from the file manager (or
mpv --player-operation-mode=pseudo-gui -- file.mkv). - The window stays empty for ~3.5 s;
runtime_statusbecomesactive.
Possible fix
VK_LOADER_DRIVERS_DISABLE='*nvidia*' is vendor-neutral (works for Intel and AMD iGPUs) and only affects the process it is set for. It could be applied to mpv when NVIDIA does not drive the display, e.g. with the omarchy-hw-nvidia-display detector from #11690, through Omarchy's mpv.desktop / a small launcher. It should not be set session-wide: games and prime-run need the NVIDIA Vulkan driver.
With VA-API on the iGPU as well (--hwdec=vaapi, iHD), 4K60 VP9 playback drops from ~1.6 CPU cores (software decode) to ~0.1 here, without waking the dGPU.
Filed by Claude Opus 5.5 via Claude Code.
View raw text
### System details - ASUS ROG Zephyrus G16 (GU605CP): Intel Core Ultra 9 285H, Arc 140T iGPU (i915, `boot_vga=1`, drives eDP) + RTX 5070 Laptop (nvidia-open 610.57.04, `boot_vga=0`, runtime-suspended when idle) - Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, mpv 0.41.0-6, mesa/vulkan-intel 26.2.2, vulkan-icd-loader 1.4.357 ### What's wrong? Opening any video with Omarchy's default player (mpv, `vo=gpu-next` on Vulkan) wakes the dGPU: libplacebo enumerates every Vulkan device, the NVIDIA ICD resumes the card, and the first frame appears only after the resume (~3.5 s). The dGPU then stays awake while mpv runs. This is independent of the VA-API/GLX env: with `LIBVA_DRIVER_NAME` and `__GLX_VENDOR_LIBRARY_NAME` unset (what #11690 does on this laptop), it still happens. Measured on the same 4K60 VP9 file, launched like `mpv.desktop`, dGPU idle (`suspended`) before each run: | env | first frame | dGPU | |---|---|---| | Omarchy 4.0.4 default | 3.8–4.0 s | resumed | | `LIBVA_DRIVER_NAME`/`__GLX_VENDOR_LIBRARY_NAME` unset (#11690) | 3.7 s | resumed | | + `VK_LOADER_DRIVERS_DISABLE='*nvidia*'` | 0.5–0.8 s | stays suspended | (`first frame` = mpv's `playback restart complete` in `--log-file`; dGPU state from `/sys/bus/pci/devices/0000:01:00.0/power/runtime_status`.) ### Steps to reproduce 1. On a hybrid laptop where the iGPU drives the display, let the dGPU suspend (`runtime_status` = `suspended`). 2. Open a video from the file manager (or `mpv --player-operation-mode=pseudo-gui -- file.mkv`). 3. The window stays empty for ~3.5 s; `runtime_status` becomes `active`. ### Possible fix `VK_LOADER_DRIVERS_DISABLE='*nvidia*'` is vendor-neutral (works for Intel and AMD iGPUs) and only affects the process it is set for. It could be applied to mpv when NVIDIA does not drive the display, e.g. with the `omarchy-hw-nvidia-display` detector from #11690, through Omarchy's `mpv.desktop` / a small launcher. It should not be set session-wide: games and `prime-run` need the NVIDIA Vulkan driver. With VA-API on the iGPU as well (`--hwdec=vaapi`, iHD), 4K60 VP9 playback drops from ~1.6 CPU cores (software decode) to ~0.1 here, without waking the dGPU. Filed by Claude Opus 5.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.
- Out of scopeDecided by agents · verified · 2026-10-09 21:25 UTC