I managed to get hardware video decode working in Chrome without any issues in F35, but after the upgrade to F36 the GPU process now crashes with an error.
I was using Wayland before when it worked, and saw the notice about sandbox permissions in Firefox, but this seems to be some other issue with the update of Mesa and/or libva.
Is there anything I can try besides waiting for an update to the GPU driver, library and/or Chrome? VAAPI decoding with MPV seems to work (for H.264 at least).
[9172:9172:0522/155609.854343:ERROR:vaapi_wrapper.cc(2516)] vaPutSurface failed, VA error: invalid VADisplay [9172:9172:0522/155609.854413:ERROR:vaapi_video_decode_accelerator.cc(288)] Failed putting surface into pixmap [9327:1:0522/155610.602465:ERROR:command_buffer_proxy_impl.cc(328)] GPU state invalid after WaitForGetOffsetInRange. [9137:9137:0522/155610.607189:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=139
libva info: VA-API version 1.14.0 libva info: User environment variable requested driver 'radeonsi' libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.14 (libva 2.14.0) vainfo: Driver version: Mesa Gallium driver 22.0.3 for AMD Radeon RX 5700 (navi10, LLVM 14.0.0, DRM 3.44, 5.17.8-300.fc36.x86_64) vainfo: Supported profile and entrypoints [...]
Chromium version 101.0.4951.67, flags:
--disable-features=UseChromeOSDirectVideoDecoder --enable-features=VaapiVideoDecoder --ignore-gpu-blocklist
Relevant ENV entries:
Version diffs between F35 and F36:
mesa-dri-drivers: 21.2.3-6.fc35 > 22.0.1-1.fc36 libva: 2.13.0-1.fc35 > 2.14.0-1.fc36