Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1035917: chromium: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

2,417 views
Skip to first unread message

Mathias Behrle

unread,
May 11, 2023, 3:40:05 AM5/11/23
to
Package: chromium
Version: 113.0.5672.63-2
Severity: important

Dear Maintainer,

I am currently out of luck to guess the correct addressee for this
problem, so please advise.

chromium doesn't start any more since some days with
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

As this happens with intel-media-va-driver as well as intel-media-va-driver-non-free
it seems to me more a problem on the chromium side. It happens also with
the flatpak package:
flatpak run com.github.Eloston.UngoogledChromium
then with
libva error: /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/iHD_drv_video.so init failed



Cheers,
Mathias

-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-8-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii chromium-common 113.0.5672.63-2
ii libasound2 1.2.8-1+b1
ii libatk-bridge2.0-0 2.46.0-5
ii libatk1.0-0 2.46.0-5
ii libatomic1 12.2.0-14
ii libatspi2.0-0 2.46.0-5
ii libbrotli1 1.0.9-2+b6
ii libc6 2.36-9
ii libcairo2 1.16.0-7
ii libcups2 2.4.2-3
ii libdbus-1-3 1.14.6-1
ii libdouble-conversion3 3.2.1-1
ii libdrm2 2.4.114-1+b1
ii libevent-2.1-7 2.1.12-stable-8
ii libflac12 1.4.2+ds-2
ii libfontconfig1 2.14.1-4
ii libfreetype6 2.12.1+dfsg-5
ii libgbm1 22.3.6-1+deb12u1
ii libgcc-s1 12.2.0-14
ii libglib2.0-0 2.74.6-2
ii libgtk-3-0 3.24.37-2
ii libjpeg62-turbo 1:2.1.5-2
ii libjsoncpp25 1.9.5-4
ii liblcms2-2 2.14-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.35-1
ii libnss3 2:3.87.1-1
ii libopenh264-7 2.3.1+dfsg-3
ii libopenjp2-7 2.5.0-1+b1
ii libopus0 1.3.1-3
ii libpango-1.0-0 1.50.12+ds-1
ii libpng16-16 1.6.39-2
ii libpulse0 16.1+dfsg1-2+b1
ii libre2-9 20220601+dfsg-1+b1
ii libsnappy1v5 1.1.9-3
ii libstdc++6 12.2.0-14
ii libwebp7 1.2.4-0.1
ii libwebpdemux2 1.2.4-0.1
ii libwebpmux3 1.2.4-0.1
ii libwoff1 1.0.2-2
ii libx11-6 2:1.8.4-2
ii libxcb1 1.15-1
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.6-1
ii libxext6 2:1.3.4-1+b1
ii libxfixes3 1:6.0.0-2
ii libxkbcommon0 1.5.0-1
ii libxml2 2.9.14+dfsg-1.2
ii libxnvctrl0 525.85.05-1
ii libxrandr2 2:1.5.2-2+b1
ii libxslt1.1 1.1.35-1
ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend] 1.14.1-1
ii zlib1g 1:1.2.13.dfsg-1

Versions of packages chromium recommends:
ii chromium-sandbox 113.0.5672.63-2

Versions of packages chromium suggests:
pn chromium-driver <none>
ii chromium-l10n 113.0.5672.63-2
pn chromium-shell <none>

Versions of packages chromium-common depends on:
ii libc6 2.36-9
ii libdouble-conversion3 3.2.1-1
ii libjsoncpp25 1.9.5-4
ii libstdc++6 12.2.0-14
ii libx11-6 2:1.8.4-2
ii libxnvctrl0 525.85.05-1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.13.dfsg-1

Versions of packages chromium-common recommends:
ii awesome [notification-daemon] 4.3-7
ii chromium-sandbox 113.0.5672.63-2
ii fonts-liberation 1:1.07.4-11
ii libgl1-mesa-dri 22.3.6-1+deb12u1
ii libu2f-udev 1.1.10-3
ii mate-notification-daemon [notification-daemon] 1.26.0-1
ii notification-daemon 3.20.0-4+b1
ii system-config-printer 1.5.18-1
ii upower 0.99.20-2

Versions of packages chromium-sandbox depends on:
ii libc6 2.36-9

-- no debconf information

Andres Salomon

unread,
May 11, 2023, 12:00:06 PM5/11/23
to
Control: severity -1 normal



On Thu, May 11 2023 at 09:29:55 AM +02:00:00, Mathias Behrle
<mbe...@debian.org> wrote:
> Package: chromium
> Version: 113.0.5672.63-2
> Severity: important
>
> Dear Maintainer,
>
> I am currently out of luck to guess the correct addressee for this
> problem, so please advise.
>
> chromium doesn't start any more since some days with
> libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init
> failed
>


I'm guessing that the following is also broken for you:

vainfo

You could also try the following to see if the other intel driver isn't
broken:

LIBVA_DRIVER_NAME=i965 vainfo

Did this used to work for you? If so, you could try downgrading
intel-media-va-driver using snapshot.debian.org (or upgrading to the
version that's in unstable, and hasn't migrated to bookworm yet).

Either way, chromium uses vaapi by default; so if the vaapi driver for
your specific hardware is broken, you'll have to figure out which
combination of flags to disable it work for you (eg,
https://www.reddit.com/r/archlinux/comments/tc5379/if_you_have_trouble_getting_vaapi_hardware_video/
) until you get vaapi working with your hardware.

Out of curiosity, what is the GPU and CPU that you're seeing this iHD
driver failure on?

Mathias Behrle

unread,
May 11, 2023, 2:00:05 PM5/11/23
to
* Andres Salomon: " Re: Bug#1035917: chromium: libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed" (Thu, 11 May 2023
11:48:48 -0400):

Hi Andres,

thanks for your feedback.

> I'm guessing that the following is also broken for you:
>
> vainfo

Not really broken, but

libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 2.4.1
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD

> You could also try the following to see if the other intel driver isn't
> broken:
>
> LIBVA_DRIVER_NAME=i965 vainfo
>
> Did this used to work for you? If so, you could try downgrading
> intel-media-va-driver using snapshot.debian.org (or upgrading to the
> version that's in unstable, and hasn't migrated to bookworm yet).

Ok, will try that besides evtl. downgrading chromium.

> Either way, chromium uses vaapi by default; so if the vaapi driver for
> your specific hardware is broken, you'll have to figure out which
> combination of flags to disable it work for you (eg,
> https://www.reddit.com/r/archlinux/comments/tc5379/if_you_have_trouble_getting_vaapi_hardware_video/
> ) until you get vaapi working with your hardware.
>
> Out of curiosity, what is the GPU and CPU that you're seeing this iHD
> driver failure on?

mathiasb@monsterix:~$ cat /proc/cpuinfo
...
GenuineIntel cpu family : 6 model : 60 model name :
Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
...

mathiasb@monsterix:~$ glxinfo
...
Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086)
Device: Mesa Intel(R) HD Graphics 4600 (HSW GT2) (0x412) Version: 22.3.6
Accelerated: yes Video memory: 1536MB Unified memory: yes Preferred profile:
core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max
GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor
string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL core
profile shading language version string: 4.60
...


--

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6

Andres Salomon

unread,
May 11, 2023, 2:10:05 PM5/11/23
to
Okay, so an older CPU that the newer intel vaapi driver is broken on.
If you just uninstall intel-media-va-driver and
intel-media-va-driver-non-free, does chromium work? You'd be relying on
the older driver from i965-va-driver at that point.

Mathias Behrle

unread,
May 11, 2023, 5:42:28 PM5/11/23
to
* Andres Salomon: " Re: Bug#1035917: chromium: libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed" (Thu, 11 May 2023
14:03:51 -0400):

> Okay, so an older CPU that the newer intel vaapi driver is broken on.
> If you just uninstall intel-media-va-driver and
> intel-media-va-driver-non-free, does chromium work? You'd be relying on
> the older driver from i965-va-driver at that point.

Tried that already, didn't work either.
0 new messages