After libva 2.22 vainfo doesn't launch (libEGL_mesa.so.0: undefined symbol: wl_drm_interface)
Description:
After libva 2.22 vainfo exits with error (libEGL_mesa.so.0: undefined symbol: wl_drm_interface
)
If downgrading libva, it launches. Maybe mesa needs to sync with libva.
$ vainfo
Trying display: wayland
error: failed to resolve wl_drm_interface(): /usr/lib/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
libva error: /usr/lib/dri/i965_drv_video.so init failed
vaInitialize failed with error code -1 (unknown libva error),exit
Additional info:
- libva 2.22.0-1
- libva-utils 2.22.0-1
- mesa 1:24.1.4-2
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- 🤖 Bugbuddy 🤖 added priority3-normal severity4-low statusunconfirmed labels
added priority3-normal severity4-low statusunconfirmed labels
- 🤖 Bugbuddy 🤖 assigned to @freswa, @toolybird, and @gromit
assigned to @freswa, @toolybird, and @gromit
Related:
https://bbs.archlinux.org/viewtopic.php?id=286363
https://github.com/intel/libva/issues/375
https://github.com/intel/libva/issues/496As far as I can tell from that, the issue is not with
libva
itself.
/usr/lib/dri/i965_drv_video.so
belongs tolibva-intel-driver
package.Edited by Hanabishi ReccaCollapse replies - Author
What is interesting here is
error: failed to resolve wl_drm_interface(): /usr/lib/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
from the commits of libva:
https://github.com/intel/libva/commit/1b7d71f68b6ebc7f7c3b80e3eb6b3d888b0463e1
wl_drm is a legacy protocol, and wlroots is getting rid of it [1]. Use the newer and standard linux-dmabuf protocol if available to get the DRM device.
as /usr/lib/libEGL_mesa.so.0 belongs to mesa, and it's not happy, maybe mesa should be compiled against new libva?
Idk, I can't reproduce the issue. I don't have a i965 iGPU.
Are you sure you don't want
intel-media-driver
instead oflibva-intel-driver
?- Author
doesn't open at all, even with downgraded libva.
$ vainfo Trying display: wayland libva error: /usr/lib/dri/iHD_drv_video.so init failed vaInitialize failed with error code -1 (unknown libva error),exit
Hmm, maybe it's indeed not compatble. iHD driver is for Broadwell+. What CPU/iGPU do you have?
Although, it's
libva
depends onmesa
, not vice versa. So I doubt it being a root of the problem. But you could try to rebuild it yourself, if you think it should help.Btw, does the actual video acceleration works? Or it's only the
vainfo
command problem?- Author
Judging by intel_gpu_top seems, it has no accel now. Reverting libva helps.
mpv --fs --hwdec=vaapi --loop ~/Videos/video.mp4 (+) Video --vid=1 (*) (h264 1920x816 23.976fps) (+) Audio --aid=1 (*) (aac 6ch 48000Hz) error: failed to resolve wl_drm_interface(): /usr/lib/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/dri/i965_drv_video.so init failed
Will try to build mesa.
Edited by muziknavi I found the root cause: https://github.com/intel/intel-vaapi-driver/pull/566
Fetching wl_drm_interface from libEGL used to work but doesn't anymore: it's now a private symbol (wayland-scanner private-code).
Edited by Hanabishi ReccaWill try to build mesa.
It won't help. Instead, try to rebuild
libva-intel-driver
with the patch above applied.Edited by Hanabishi Recca- Author
Recompiled libva-intel-driver with the patch, it helped.
Ok, I guess you could close this issue then and open a new issue in libva-intel-driver with a backport request, if you want.
Edited by Hanabishi Recca
- Christian Heusel added scopebug statusconfirmed labels and removed statusunconfirmed label
added scopebug statusconfirmed labels and removed statusunconfirmed label
- 🤖 Bugbuddy 🤖 assigned to @alucryd and unassigned @freswa, @toolybird, and @gromit
assigned to @alucryd and unassigned @freswa, @toolybird, and @gromit
- muziknavi mentioned in issue libva-intel-driver#1
mentioned in issue libva-intel-driver#1
- muziknavi closed
closed