FS#53253 - [libva-intel-driver] Broken with libglvnd
Attached to Project:
Arch Linux
Opened by Dor Askayo (xtor91) - Saturday, 11 March 2017, 13:09 GMT
Last edited by Laurent Carlier (lordheavy) - Saturday, 11 March 2017, 13:47 GMT
Opened by Dor Askayo (xtor91) - Saturday, 11 March 2017, 13:09 GMT
Last edited by Laurent Carlier (lordheavy) - Saturday, 11 March 2017, 13:47 GMT
|
Details
Using:
* mesa 17.0.1-2 * libglvnd 0.2.999+g4ba53457-1 * libva 1.7.3-2 * libva-intel-driver 1.7.3-1 I'm getting this error: $ vainfo libva info: VA-API version 0.39.4 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_39 error: failed to resolve wl_drm_interface(): /usr/lib/libEGL.so.1: undefined symbol: wl_drm_interface libva error: /usr/lib/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit It appears to be the same issue fixed in Fedora [1], with one patch for libva [2] and one for libva-intel-driver [3]. The former patch was already applied in the Arch repositories [4], but the latter hasn't been applied yet. I haven't actually tested the patch yet, but it does seem reasonable. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1422151#c10 [2] http://pkgs.fedoraproject.org/cgit/rpms/libva.git/commit/?id=27e9184e8dcea697f7b4b205f264f1b0c9a163b2 [3] https://pkgs.rpmfusion.org/cgit/free/libva-intel-driver.git/commit/?id=f59aa742507de2dfe9a0dbb9ca807c952fe49213 [4] https://git.archlinux.org/svntogit/packages.git/tree/trunk/not-finding-wl-drm-interface-with-libglvnd.patch?h=packages/libva&id=40e92391ce83aa1a314e13e350294c33fa599f34 |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Saturday, 11 March 2017, 13:47 GMT
Reason for closing: Fixed
Additional comments about closing: libva-intel-driver-1.7.3-2
Saturday, 11 March 2017, 13:47 GMT
Reason for closing: Fixed
Additional comments about closing: libva-intel-driver-1.7.3-2
Comment by
Laurent Carlier (lordheavy) -
Saturday, 11 March 2017, 13:45 GMT
thanks for tracking down the fix!