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.
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/1c4f53bc72 e36385d301ac0ae cfbf40d748e4483 /vainfo/ vainfo. c#L37-L38 and https:/ /github. com/intel/ libva-utils/ blob/1c4f53bc72 e36385d301ac0ae cfbf40d748e4483 /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:/ /launchpadlibra rian.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.