mpv - symbol lookup error (undefined symbol : vaSyncBuffer)

[neo]

system :

jammy 64bit,
ryzen 5600, radeon 550x graphics (polaris, legacy)

...

upon installing your 3 ppa (ffmepg4, ffmpeg5, mpv)
and installing

libmpv2 and mpv

getting error

mpv: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer

have installed latest graphics card driver from amd (amdgpu-install --opencl=legacy --vulkan=amdvlk)

please let me know where erred,
thanks

[Rob Savoury (savoury1)]

Interesting, thanks for reporting the bug. However, I am unable to reproduce this error on my 22.04 Jammy test system (though it naturally doesn't have the AMD GPU hardware you use). There is a recent Debian bug report (with no response from the maintainers as yet) about the same missing symbol error you're seeing, but with minidnla package rather than mpv. See here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017183

Various other upstream bugs have been reported in the past year or so with libva (provides VA-API, including the vaSyncBuffer symbol) when used with AMD GPU hardware and certain Linux kernel versions. However, those bugs are usually about failure of VA-API to work, rather than this missing symbol error that you're seeing.

A few days ago a new libva version 2.16.0 was released (2.15.0 is currently at ppa:savoury1/ffmpeg4), and also a new FFmpeg 5.1.2 version has been released (5.1.1 is currently at ppa:savoury1/ffmpeg5). This weekend I aim to package both these new versions, and the build of FFmpeg 5.1.2 will be with the latest libva 2.16.0 so there's a chance that some bug fixes in either (or both) of these new libva and FFmpeg versions will fix this missing symbol issue.

Or it might be related to what version of libva the proprietary AMD GPU drivers were built against, in which case there will be nothing that I can do to fix the issue. Once the new libva and FFmpeg are built and published I'll update this bug report and then you can do an apt-get update/upgrade to see if the newer versions resolve the missing symbol problem.

[Rob Savoury (savoury1)]

An update on the packaging of new versions: latest libva 2.16.0 is now published (at ppa:savoury1/ffmpeg4), and latest FFmpeg 5.1.2 built against that version is also available (at ppa:savoury1/ffmpeg5). Additionally, new builds of mpv 0.35~pre (pre-release of 0.35 from git source today, 3 Oct 2022) have just been completed at ppa:savoury1/mpv and these were naturally done with the new libva and FFmpeg versions.

Please upgrade to these new versions and test if you still have the issue with a missing symbol. If the error persists then there is likely nothing more I can do to fix it at the packaging level. In that case, perhaps you could report the issue upstream to the mpv devs [*] (include your GPU hardware info, proprietary AMD driver versions, etc, if you do that) to see if they might be able to help.

[*] https://github.com/mpv-player/mpv/issues

[Rob Savoury (savoury1)]

Also, on looking back at the info in your bug report there is something strange with this line:

mpv: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer

The path there is not correct for my builds of FFmpeg 5! Unfortunately I didn't quite notice that small but important detail when first reading your report.

Do you have another FFmpeg 5 installed from another PPA or via a local build that you did yourself? The Jammy FFmpeg 5 package at ppa:savoury1/ffmpeg5 uses the standard /usr/lib path for libraries and so for an amd64 system the libavcodec.so.59 path is exactly as follows:

/usr/lib/x86_64-linux-gnu/libavcodec.so.59

It seems that there is something strange going on with your FFmpeg configuration anyhow, so that might well be the actual cause of the issue you're seeing.

[neo (csae2608)]

yes, i probably had an build via svp4, but probably the build failed, so i resorted to another option (mpv+vapoursynth easy via ppa)
could be that the ffmpeg got installed,
not so savvy;
please close this report as i am about to reinstall the OS,
and should i encounter again an error might report anew.
(prefer to build mpv via instructions on svp4 page, which just got updated)
thank you very much for your help;

[Rob Savoury (savoury1)]

OK, closing this report. Good luck with the OS reinstall, hopefully everything will work fine for you after that.