Saikrishna Arcot

There is no build in my PPA for 20.04 yet.

Is this with Chromium `85.0.4164.2-0ubuntu1~ppa2~20.04.1`?

Can someone start Chromium with the `LIBVA_MESSAGING_LEVEL=2` environment variable set and paste the output here? (for example, `LIBVA_MESSAGING_LEVEL=2 chromium-browser --enable-logging=stderr --log-level=0 --vmodule=vaapi_wrapper=4,vaapi_video_decode_accelerator=4`)

I can repro @mamarley's output, but not @Sraw's output. I'm not sure why the difference is there; maybe try with h264 videos (or use the h264-ify extension) to make sure...

This is the output of `vainfo` on my Intel laptop with the `iHD` driver. Can you confirm that in both of your outputs, `VAProfileNone` is **not** present? ``` libva info:...

Ok, I think I figured out the difference in error conditions. Both I and @Sraw had `intel-media-va-driver` installed, which does not support `VAProfileNone`, but Chromium assumes that it is indeed...

Another update on this, the iHD driver seems to only allow NV12 color format, but some other color format appears to be being passed in (I420, I'm guessing, but can't...

For reference, to get these logs, the `intel-media-va-driver` package needs to be recompiled as `release-internal` build type (Ubuntu's/Debian's build rules don't specify a build type, so it default to release)....

Dev has been updated to 86.0.4214.2, Beta is being updated to 85.0.4183.49.

Chromium itself is blocking the iHD driver because of errors in the driver itself. I can remove it, but then you will see those errors if that driver is used....