Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
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
|
DetailsI 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
Tuesday, 20 August 2019, 16:14 GMT
Reason for closing: No response
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?