Package Details: chromium-vaapi 80.0.3987.106-2

Git Clone URL: (read-only, click to copy)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
Upstream URL:
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 92
Popularity: 3.36
First Submitted: 2016-07-09 09:44
Last Updated: 2020-02-15 09:56

Dependencies (49)

Required by (61)

Sources (16)

Pinned Comments

maximbaz commented on 2019-12-24 19:17

If you are having issues with NVidia, you need to build a patched libva-vdpau-driver-chromium, see here for details.

maximbaz commented on 2019-07-18 13:19

This package is compiled with 'use_vaapi=true', but you need to pass --ignore-gpu-blacklist if you want to enable hardware video acceleration using VA-API.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

maximbaz commented on 2020-02-15 20:24

Right, I see, thanks - with this flag, I do indeed see MojoVideoDecoder, but the playback is very laggy. And thanks for letting me know about the corrupted package, will fix it as well.

liewkj commented on 2020-02-15 19:55

@maximbaz You forgot the switch "--use-gl=egl". Without it, i965 VA driver failed DRI2 sanity check during vaInitialize() on wayland. My own build works fine for me across all my systems. I wanted to try out yours but the package seemed to be corrupted.

maximbaz commented on 2020-02-15 09:56

Sure, let's try, I am happy to add any patch that adds VA-API support for more devices/configurations. However at least for me on Wayland this patch does nothing, I still get this error:

$ LIBVA_DRIVER_NAME=i965 chromium
[545468:545468:0215/] Too short EDID data: manufacturer id
libva error: /usr/lib/dri/ init failed
[545492:545492:0215/] vaInitialize failed: unknown libva error
[545492:545492:0215/] InitializeSandbox() called with multiple threads in process gpu-process.

Could you confirm if this helps you at least?

liewkj commented on 2020-02-15 03:19

@maximbaz Will you add upstream fix for bug 1041229 for the meantime?

Terence commented on 2020-01-27 20:26

Hey folks, I didn't see one so I made, based on

This allows you to get VP9 hardware accelerated video decoding on Nvidia. It was tested successfully on my GTX 960.

maximbaz commented on 2020-01-17 12:10

I'm not familiar with chromium specifics to make this judgement, if you feel that this should be enabled for everyone, let's not limit this to chromium-vaapi only, please propose this for extra/chromium, whether by opening a bug report or contacting maintainer by email (see in PKGBUILD), and in your request explain why this would be beneficial so that it's easier to make the decision :) As soon as it appears in extra/chromium, it will get propagated to this pkg as well.

danhyal commented on 2020-01-15 09:33

@maximbaz I don't think there would be any issues including the flag since you are already depending on freetype, The chromium package 'ungoogled-chromium' also includes the flag and they don't seem to have any issues.

maximbaz commented on 2019-12-24 19:17

If you are having issues with NVidia, you need to build a patched libva-vdpau-driver-chromium, see here for details.

slipknot commented on 2019-12-24 18:24

Just reporting that I have the same problem of the GMA4500 also in HD2000 Sandybridge. Somebody knows what was the last version that worked with intel graphics? I don't have a powerful cpu so compiling times takes a lot, I appreciate any guidance you could give me. Regards.

maximbaz commented on 2019-12-24 13:14

xorgproto removal has been reverted:

@danhyal: I would like to keep this package as close as possible to extra/chromium, and I don't know much about implications of adding use_system_freetype=true, have you considered proposing this to extra/chromium?