FS#51664 - [libvdpau-va-gl] va_getDriverName() returns -1

Attached to Project: Community Packages
Opened by Britt Yazel (brittyazel) - Thursday, 03 November 2016, 04:01 GMT
Last edited by Maxime Gauduin (Alucryd) - Tuesday, 20 August 2019, 16:14 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I have an Haswell Intel graphics chip, and I'm not sure when this broke exactly, vdpauinfo is now reporting the following:

display: :0 screen: 0
libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
API version: 1
Information string: OpenGL/VAAPI backend for VDPAU

and a bunch more "---not supported---" lines.

I have va-api correctly set up with working acceleration, and libvdpau-va-gl used to work correctly for vdpau acceleration, but now it appears broken.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Tuesday, 20 August 2019, 16:14 GMT
Reason for closing:  No response
Comment by Britt Yazel (brittyazel) - Friday, 04 November 2016, 16:43 GMT
This same issue is the case on my work PC with an i7-6700k and Intel HD 530 graphics.
Comment by Maxime Gauduin (Alucryd) - Friday, 03 November 2017, 21:10 GMT
It works fine on my Haswell laptop. Did you export VDPAU_DRIVER=va_gl as per upstream's instructions?
Comment by Britt Yazel (brittyazel) - Monday, 13 November 2017, 17:38 GMT
Yes, I have that in my /etc/environment

So this seems to be a Wayland specific bug with vdpau. Switching to an Xorg session allows vdpauinfo to work just fine. Is there a known wayland/vdpau incompatibility?
Comment by Maxime Gauduin (Alucryd) - Friday, 17 May 2019, 14:46 GMT
Does it sill happen? vdpau is pretty much dead anyway, might want to use vaapi instead, especially on intel.

Loading...