Package Details: chromium-vaapi 65.0.3325.162-1

Git Clone URL: (read-only)
Package Base: chromium-vaapi
Description: Chromium compiled with VA-API support for Intel Graphics
Upstream URL:
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 33
Popularity: 3.874739
First Submitted: 2016-07-09 09:44
Last Updated: 2018-03-14 11:11

Dependencies (42)

Required by (33)

Sources (10)

Pinned Comments

samcv commented on 2016-08-01 05:11

NOTE: I no longer have time to maintain this package. I am looking for a co-maintainer who would be willing to take over. I am willing to help you, but I no longer have the time to spend compiling and debugging.

The version in the repo/on AUR is outdated and has certificate issues due to some timer inside Chromium that was triggered after a certain length of time from the build. You could also try chromium-dev-vaapi from ArchCN

I am now providing a repository in case you don't want to build the entire package yourself. The repository can be used by adding this to you pacman.conf:
Server =$arch/
SigLevel = Required

The package is signed with my PGP key, so you must add my key to pacman by doing:
pacman-key -r C3881D62
pacman-key --lsign-key C3881D62

If you have an Intel GPU you should use the chromium-vaapi package, but if you use Radeon/NVIDIA you should use another package in my repository called chromium-vaapi-other (If you want compile it yourself, please rename the package name in the PKGBUILD to chromium-vaapi-other and it will use the chromium-vaapi-other patch instead of the intel one). If someone can test it out and email me if it works along with the make and model of your video card that would be great. Contact information is Thank you.

Other useful info:
Run "vainfo" in terminal to see what your card supports. Most don't support VP9 encoding which is used by default on YouTube and other sites. If so you may try this plugin If your card doesn't support 60fps H.264, make sure to go into the options for the plugin and disable 60fps video.
To see if it is working properly, when a video starts playing you should see the following in your terminal:
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0

This message also shows up twice when chromium first opens when chromium checks if the computer supports VAAPI.

Latest Comments

hans20056 commented on 2018-03-13 07:05

It seems the problem is with the new version itself. It is apparent when downloading new pages (low fps animation) and switching between tabs. VA-API works normally (with couple % more CPU resources used).

maximbaz commented on 2018-03-12 18:00

I also experience this lag, but it happens seemingly on all websites, even on those without a video. Have you had a chance to double check that this is VA-API problem, and not the problem with official chromium v65 in general? I'm planning to do some tests, but I had no time so far.

hans20056 commented on 2018-03-12 17:57

The new version (65) is using more CPU resources on videos and lags considerably when downloading new pages. Just downgraded to older version (64) which works fine.

OneObsession commented on 2018-03-11 07:37

Thanks again @xsmile for the VA-API patches.

xsmile commented on 2018-03-06 22:59

These two patches are necessary for 65.0.3325.146 to enable VA-API. According to chrome:gpu hardware accelerated encoding is supported too.

ailick commented on 2018-02-13 14:06

I use gnome in wayland and install libva-git which enabled dri3.

Running in xwayland:

[1444:1444:0222/] : vaInitialize failed: unknown libva error

[1444:1444:0222/] : Failed to create VaapiWrapper for va_profile: 7

[1444:1444:0222/] : HW video decode not available for profile h264 high

flv commented on 2018-02-11 19:35

getting double title bars when enabling Hardware-accelerated video and disabling Use system title bar and borders

realh commented on 2018-01-29 22:31

@bwat48 Thanks for the quick response. It looks like Intel aren't interested in fixing this and other players have had to add their own workarounds (trying the Wayland backend if the X11 one fails?). Would that be possible for Chromium, and is there someone with the time and expertise to do it?

bwat48 commented on 2018-01-29 22:01

@realh In a wayland session, Chromium uses Xwayland.

VAAPI uses DRI2, whereas Xwayland only supports DRI3 so VAAPI does not work under Xwayland


realh commented on 2018-01-29 21:46

Is there a way to make it work with Wayland? Currently it works in xorg, but in Wayland it says

[8871:8871:0129/] : vaInitialize failed: unknown libva error

at the bottom of chrome://gpu and falls back to software decoding.

I see the libva package provides and; maybe Chromium is trying to use the wrong one? If so, can I force it to use the other, preferably without recompiling?

All comments