Index | Thread | Search

From:
qczy <qczy@proton.me>
Subject:
FIX: www/chromium: VA-API fails to initialize because of unveil
To:
"ports@openbsd.org" <ports@openbsd.org>
Cc:
"robert@openbsd.org" <robert@openbsd.org>
Date:
Sun, 27 Sep 2026 15:09:12 +0000

Download raw body.

Thread
  • qczy:

    FIX: www/chromium: VA-API fails to initialize because of unveil

On a -current system with an ALDERLAKE_S, gen 12 and the
intel-media-driver-26.2.4 package installed, chromium fails to initialize
VA-API with only this error message:

 [23470:223676:0927/161118.165188:ERROR:media/gpu/vaapi/vaapi_wrapper.cc:1801] vaInitialize failed: unknown libva error

I had a look with ktrace(1) and noticed that the chromium GPU process
successfully opens /usr/local/lib/dri/iHD_drv_video.so

 43837 chrome   CALL  open(0x85ad4190180,0x10000<O_RDONLY|O_CLOEXEC>)
 43837 chrome   NAMI  "/usr/local/lib/dri/iHD_drv_video.so"
 43837 chrome   RET   open 26/0x1a

But that is _before_ it does its unveil(2) calls. Apparently, after the unveil(2)
calls, it again tries to access(2) that file, which now fails due to unveil:

 43837 chrome   CALL  access(0x85b17b1eba0,0<F_OK>)
 43837 chrome   NAMI  "/usr/local/lib/dri/iHD_drv_video.so"
 43837 chrome   RET   access -1 errno 2 No such file or directory

Adding "/usr/local/lib/dri r" to /etc/chromium/unveil.gpu makes it work; see the
patch below.

I'm not sure if this is because of a recent change in chromium, as I thought it
used to work?



Index: files/unveil.gpu
===================================================================
RCS file: /cvs/ports/www/chromium/files/unveil.gpu,v
diff -u -p -u -p -r1.8 unveil.gpu
--- files/unveil.gpu	10 Apr 2026 07:05:14 -0000	1.8
+++ files/unveil.gpu	27 Sep 2026 15:00:16 -0000
@@ -5,6 +5,7 @@
 /usr/X11R6/share/libdrm r
 /usr/X11R6/share/vulkan r
 /usr/local/chrome r
+/usr/local/lib/dri r
 
 # needed for IPC communication, X.Org, etc.
 /tmp rwc