i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface]

it's a bug in the mesa build which is using meson now, it doesn't link with libwayland_drm, not sure why

moving back to the driver

https://github.com/intel/intel-vaapi-driver/issues/419

probably needs a newer libva too

Status changed to 'Confirmed' because the bug affects multiple users.

Fixed in 2.4.0-1.

Is a newer intel-vaapi-driver package planed?
(- currently in Debian Sid & does fix the issue in a wayland session..

This bug was fixed in the package intel-vaapi-driver - 2.3.0-0ubuntu1

---------------
intel-vaapi-driver (2.3.0-0ubuntu1) disco; urgency=medium

  * Merge with Debian, remaining changes:
    - use upstream tarball with shader support

 -- Timo Aaltonen <email address hidden> Tue, 12 Mar 2019 14:15:20 +0200

The bug is still present in i965-va-driver 2.3.0-0ubuntu1 on disco.

The ubuntu package doesn't include needed patch, i.e
0004-Check-the-interface-from-libva-first.patch

Apply that and it'll work fine..

This bug was fixed in the package intel-vaapi-driver - 2.3.0-0ubuntu2

---------------
intel-vaapi-driver (2.3.0-0ubuntu2) disco; urgency=medium

  * Restore debian/patches, disable all but an upstream commit to fix
    loading on wayland. (LP: #1813131)

 -- Timo Aaltonen <email address hidden> Wed, 13 Mar 2019 09:25:05 +0200

This bug now affects Bionic (and the core18 snap as a result) after picking up Mesa 19 from Disco in the 18.04.3 HWE release.

$ vainfo
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
error: failed to resolve wl_drm_interface(): /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) (0x5917)
    Version: 19.0.2
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 19.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

so libva/intel-vaapi-driver needs fixing in bionic now

Status changed to 'Confirmed' because the bug affects multiple users.

Same for me on Bionic.

Linux 4.15.0-65-generic x86_64

vainfo
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) 965Q (0x2992)
    Version: 19.0.8
    Accelerated: yes
    Video memory: 384MB
    Unified memory: yes
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 965Q
OpenGL version string: 2.1 Mesa 19.0.8
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 2.0 Mesa 19.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

That *might* be a different bug. This bug is specifically about:

error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface

This is still an issue which requires a fix asap. It is affecting bionic release 18.04.4 LTS

please see my bug report here:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1866356

Could we get an update on this, thanks.

Comments #17 and #19 might be a different bug (bug 1866356). I'm not sure yet...

Sorry for the confusion, I was travelling at the time of comment #20. Mention of "wl_drm_interface" in bug 1866356 convinces me that it's just a duplicate of this one. And this one is still open for bionic.

I can confirm this is not working on Bionic. vainfo output:

libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
error: failed to resolve wl_drm_interface(): /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit