Bugzilla – Bug 1175082
VAAPI not working in Chromium
Last modified: 2024-03-08 13:29:44 UTC
I am unable to use VAAPI in Chromium. This is on a Ryzen 7 3700U APU. When I run it in the terminal and play a YouTube video I get the following: [27610:27610:0810/214440.594411:ERROR:vaapi_wrapper.cc(497)] Could not get a valid VA display [27610:27610:0810/214440.636872:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [27613:27672:0810/214442.733807:ERROR:cert_verify_proc_builtin.cc(637)] CertVerifyProcBuiltin for ping.ublock.org failed: ----- Certificate i=0 (CN=*.ublock.org,OU=COMODO SSL Wildcard,OU=Domain Control Validated) ----- ERROR: Time is after notAfter [27613:27673:0810/214442.734367:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -201 [27892:16:0810/214451.748247:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder name\":\"DecryptingVideoDecoder\"},\"stack\":[{\"file\":\"../../media/filters/decoder_selector.cc\",\"line\":172}],\"status_code\":265,\"status_message\":\"\"}"} [27892:16:0810/214451.748812:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/mojo/clients/mojo_video_decoder.cc\",\"line\":158}],\"status_code\":261,\"status_message\":\"\"}],\"data\":{\"Decoder name\":\"MojoVideoDecoder\"},\"stack\":[{\"file\":\"../../media/filters/decoder_selector.cc\",\"line\":172}],\"status_code\":265,\"status_message\":\"\"}"}
Please attach output of vainfo (package libva-utils).
libva info: VA-API version 1.8.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_8 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.8 (libva 2.8.0) vainfo: Driver version: Mesa Gallium driver 20.1.7 for AMD RAVEN (DRM 3.38.0, 5.8.7-1-default, LLVM 10.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 VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc
Hmm. This looks good. Nothing obviously wrong with libva support.
Reassigning to maintainer/bugowner of chromium.
CHROMIUM: Hello, Can you please check whether this still applies with the latest version of Chromium. Thanks, Callum
It's hard to tell whether it's using vaapi or not, but I still get: [12520:12520:1112/210531.650303:ERROR:vaapi_wrapper.cc(546)] vaInitialize failed: unknown libva error [12520:12520:1112/210531.653352:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
>[12520:12520:1112/210531.650303:ERROR:vaapi_wrapper>.cc(546)] vaInitialize > failed: unknown libva error Failed to initiate so nope but unknown error isn't useful.
No progress