[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
Hernan, Andrei, This bug is closed and was about a machine-specific issue on 21.04. Please open a new bug to track your issue in 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
And mpv works just fine with upstream libva under Wayland without any other changes. bor@bor-Latitude-E5450:~$ mpv video.mkv (+) Video --vid=1 (*) (h264 1920x1080 25.000fps) (+) Audio --aid=1 --alang=en (*) (ac3 2ch 48000Hz) [vo/gpu/wayland] GNOME's wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback. wl_drm@22: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) and bor@bor-Latitude-E5450:~$ LD_LIBRARY_PATH=/home/bor/pkg/lib mpv video.mkv (+) Video --vid=1 (*) (h264 1920x1080 25.000fps) (+) Audio --aid=1 --alang=en (*) (ac3 2ch 48000Hz) [vo/gpu/wayland] GNOME's wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback. Cannot load libcuda.so.1 Using hardware decoding (vaapi). VO: [gpu] 1920x1080 vaapi[nv12] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
I get the same error on Ubuntu 20.04.3. The problem here is likely caused by Mesa drivers update to 21.2.6. Looks like Mesa 21 has changes in Wayland authentication and it requires fix to libva (https://github.com/intel/libva/pull/476). The fix should be present in libva 2.11 and above while Ubuntu 20.04.3 ships libva 2.6. I verified it using compiled libva/libva-utils from current upstream git. with current upstream bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo libva info: VA-API version 1.15.0 libva info: Trying to open /home/bor/pkg/lib/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /home/bor/pkg/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.15 (libva 2.15.0.pre1) vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointVLD bor@bor-Latitude-E5450:~/src/intel/libva-utils$ With *only* commit 283f776a9649dcef58b47958c1269499adfa1cd4 reverted bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.15.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~/src/intel/libva-utils$ Please update libva/vainfo in 20.04.3 to match Mesa. I can open new bug for 20.04 if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
Unfortunately i cant do a clean install since this is my main machine. As a workarround i set hwdec=drm in /etc/mpv/mpv.conf and it works just fine, don't know if the vaapi error affects any other programs. if i set the display to drm in vainfo i get no errors. vainfo --display drm libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0: VAEntrypointVLD VAProfileVP9Profile2: VAEntrypointVLD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
You say "with no video driver PPAs". As an experiment, you could try, as I did, with NO PPAs (e.g. by doing a clean reinstall from ISO). Perhaps it's due to a PPA that is not obviously related. Also, could the fact that you are on 20.04.3 be a problem? If so, but you require the LTS, you could use the --hwdec=no workaround until 22.04 LTS is available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
Hello, i am getting the same mpv error when trying to play mp4 files. Using 20.04.3 LTS with no video driver PPAs. vainfo shows this error: wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit mpv shows the same error: (+) Video --vid=1 (*) (h264 1920x1038 23.976fps) (+) Audio --aid=1 --alang=spa (*) (aac 2ch 44100Hz) (+) Subs --sid=1 (*) (subrip) [vo/gpu/wayland] GNOME's wayland compositor is known to have many serious issues with mpv. Switch to GNOME's xorg session for the best experience. wl_drm@22: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) [vo/gpu/wayland] Error occurred on the display fd, closing Exiting... (Quit) ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+attachment/5561431/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
ppa-purge failed (didn't want to replace running kernel and it couldn't find aptitude), leaving the system unstable. Did a clean reinstall of 21.04 from ISO to get a usable system (obviously without PPAs), restored home dir from nightly backup. Back in business ... mpv can now do mp4 files without error and vainfo also works without error. So you were right. But I think ppa-purge needs work. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944088] Re: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
Also I did just freshly install a 21.04 machine and vainfo/mpv work there using either of these drivers: sudo apt install intel-media-va-driver # Same as yours sudo apt install intel-media-va-driver-non-free -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944088 Title: [vaapi] libva: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1944088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
