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.
Chromium renders video black on NVIDIA: LIBVA_DRIVER_NAME=nvidia points it at a Firefox-only VA-API driver
Reported by jampick · filed Sep 24, 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 happens
On a machine with an NVIDIA GPU, video in any Chromium-family browser renders as a black rectangle. Audio plays normally, the player UI and its controls draw fine, and the page is otherwise healthy. Prime Video, Netflix and a plain <video> tag serving a local H.264 file all do it, so it is not DRM.
Why
default/hypr/nvidia.lua:13 exports LIBVA_DRIVER_NAME=nvidia for the whole session on cards with GSP firmware, and install/hardware/nvidia.sh installs libva-nvidia-driver alongside it. That driver supports Firefox only; Chromium is out of scope for it upstream. Chromium picks the variable up, decodes in hardware, and then cannot import the resulting dmabuf:
ERROR:ui/gl/angle_platform_impl.cc:48] eglCreateImage failed with 0x00003009
ERROR:ui/ozone/common/native_pixmap_egl_binding.cc:76] Unable to initialize binding from pixmap
ERROR:gpu/command_buffer/service/shared_image/ozone_image_backing.cc:320] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation0x3009 is EGL_BAD_MATCH. The video layer never gets a texture, so it stays empty while the audio track plays on.
Firefox is unaffected, which is why this hides so well: the variable is doing its job for the browser it was meant for.
Reproducing it
ffmpeg -f lavfi -i testsrc2=size=1920x1080:rate=30 -t 8 -c:v libx264 -pix_fmt yuv420p /tmp/test.mp4
printf '<video src="test.mp4" autoplay muted loop style="width:100%%"></video>' > /tmp/test.html
chromium --user-data-dir=/tmp/chromium-test --enable-logging=stderr --app=file:///tmp/test.htmlIn 8 seconds I get 442 to 568 eglCreateImage failed lines and no picture.
Numbers
RTX 3080, nvidia-open-dkms 610.57.04, chromium 152.0.7977.82, libva-nvidia-driver 0.0.18, Omarchy 4.0.0.alpha.
| run | eglCreateImage failures in 8s | video |
|---|---|---|
| as shipped | 442 to 568 | nothing rendered |
--disable-accelerated-video-decode | 0 | plays |
--disable-gpu | 0 | plays |
NVD_BACKEND=egl | 0 | plays |
Suggested fix
--disable-accelerated-video-decode in the Chromium-family flags files on this hardware. NVIDIA has no other hardware video decode path in Chromium on Linux, so nothing that was working is given up, and Firefox keeps its VA-API acceleration. NVD_BACKEND=egl also clears it and would keep hardware decode, but it is session-wide and still leans on a combination the driver does not support.
PR follows.
View raw text
## What happens On a machine with an NVIDIA GPU, video in any Chromium-family browser renders as a black rectangle. Audio plays normally, the player UI and its controls draw fine, and the page is otherwise healthy. Prime Video, Netflix and a plain `<video>` tag serving a local H.264 file all do it, so it is not DRM. ## Why `default/hypr/nvidia.lua:13` exports `LIBVA_DRIVER_NAME=nvidia` for the whole session on cards with GSP firmware, and `install/hardware/nvidia.sh` installs `libva-nvidia-driver` alongside it. That driver supports Firefox only; Chromium is out of scope for it upstream. Chromium picks the variable up, decodes in hardware, and then cannot import the resulting dmabuf: ``` ERROR:ui/gl/angle_platform_impl.cc:48] eglCreateImage failed with 0x00003009 ERROR:ui/ozone/common/native_pixmap_egl_binding.cc:76] Unable to initialize binding from pixmap ERROR:gpu/command_buffer/service/shared_image/ozone_image_backing.cc:320] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation ``` `0x3009` is `EGL_BAD_MATCH`. The video layer never gets a texture, so it stays empty while the audio track plays on. Firefox is unaffected, which is why this hides so well: the variable is doing its job for the browser it was meant for. ## Reproducing it ```bash ffmpeg -f lavfi -i testsrc2=size=1920x1080:rate=30 -t 8 -c:v libx264 -pix_fmt yuv420p /tmp/test.mp4 printf '<video src="test.mp4" autoplay muted loop style="width:100%%"></video>' > /tmp/test.html chromium --user-data-dir=/tmp/chromium-test --enable-logging=stderr --app=file:///tmp/test.html ``` In 8 seconds I get 442 to 568 `eglCreateImage failed` lines and no picture. ## Numbers RTX 3080, nvidia-open-dkms 610.57.04, chromium 152.0.7977.82, libva-nvidia-driver 0.0.18, Omarchy 4.0.0.alpha. | run | eglCreateImage failures in 8s | video | |---|---|---| | as shipped | 442 to 568 | nothing rendered | | `--disable-accelerated-video-decode` | 0 | plays | | `--disable-gpu` | 0 | plays | | `NVD_BACKEND=egl` | 0 | plays | ## Suggested fix `--disable-accelerated-video-decode` in the Chromium-family flags files on this hardware. NVIDIA has no other hardware video decode path in Chromium on Linux, so nothing that was working is given up, and Firefox keeps its VA-API acceleration. `NVD_BACKEND=egl` also clears it and would keep hardware decode, but it is session-wide and still leans on a combination the driver does not support. PR follows.
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 19:41 UTC