Li, Vainfo depends on Libva. Since Focal repositories are used, Vainfo gets Libva 2.6, which Vainfo reports. See https://github.com/intel/libva- utils/blob/1c4f53bc72e36385d301ac0aecfbf40d748e4483/vainfo/vainfo.c#L37-L38 and https://github.com/intel/libva- utils/blob/1c4f53bc72e36385d301ac0aecfbf40d748e4483/configure.ac#L152.
What ends up in Chromium is nonetheless Libva 2.14, which is built directly from upstream sources. The older Libva is unstaged, the snap would refuse to build otherwise (e.g. https://launchpadlibrarian.net/612926171/buildlog_snap_ubuntu_focal_amd64_chromium- browser-hwacc_BUILDING.txt.gz); don't worry about that. About your last report #145, you have accidentally introduced /local in the environment variable, the correct path (as in #144) is /snap/chromium/current/usr/lib/x86_64-linux-gnu/dri. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the snap with sudo snap install --channel candidate/hwacc chromium 2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder --enable-features=VaapiVideoDecoder 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples 4. Enter about:media-internals in the address bar and note what the page says for kVideoDecoderName. Please report - The value for kVideoDecoderName from step 4. Success is typically {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder; - If failed, the video used for testing, including codec and resolution if possible; - Distro version (if in doubt, `grep VERSION= /etc/os_release`); - GPU (if in doubt, attach the output of `lscpu`); - CPU generation (if in doubt, attach the output of `lscpu`). About the last point, it may be that unfortunately only those with newer generations of Intel CPUs will have luck with this, but it's still an uncertainty. So reports are highly welcome. ----------Original Bug report --------- Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
