Package Details: chromium-vaapi-bin 80.0.3987.100-1

Git Clone URL: (read-only, click to copy)
Package Base: chromium-vaapi-bin
Description: Chromium with VA-API support to enable hardware acceleration, pre-compiled
Upstream URL:
Licenses: BSD
Conflicts: chromium, chromium-vaapi
Provides: chromium, chromium-vaapi
Submitter: maximbaz
Maintainer: kureta
Last Packager: kureta
Votes: 86
Popularity: 4.34
First Submitted: 2017-06-17 14:26
Last Updated: 2020-02-14 10:59

Dependencies (40)

Required by (62)

Sources (2)

Pinned Comments

kureta commented on 2019-01-29 11:07

Please add this gpg key to install this package

gpg --recv-keys EB4F9E5A60D32232BB52150C12C87A28FEAC6B20

You can also add keyserver-options auto-key-retrieve to your ~/.gnupg/gpg.conf file.

If you have problems connecting to a Chromecast, just enable the following flag:


and restart Chromium.

Thanks to maximbaz for providing pre-compiled binaries, and thanks to niklaszantner for the tip about Chromecast.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

digitalone commented on 2019-11-15 08:44

Install icu version 65 from upstream repository.

wooque commented on 2019-11-15 08:43

@vincentv, @jam396 you need to have latest icu which is 65.1-2.

jam396 commented on 2019-11-15 08:43

I get exactly the same message

vincentv commented on 2019-11-15 08:41

Fails to start after updating to the latest version: /usr/lib/chromium/chromium: error while loading shared libraries: cannot open shared object file: No such file or directory

jam396 commented on 2019-11-15 08:34

Cannot open after installing. When I open chromium, the icon pops up and then disappears and chromium doesn't start.

danhyal commented on 2019-11-14 14:31

icu is in core now.

maximbaz commented on 2019-11-13 20:22

It's still in [testing], but once v65 moves to [core] I'll recompile :)

Hyper-V commented on 2019-11-13 19:44

icu 65.1-2 breaks chromium with this error: /usr/lib/chromium/chromium: error while loading shared libraries: cannot open shared object file: No such file or directory

maximbaz commented on 2019-11-11 14:43

I figured it out, the reason it works for me is because this pkg is out-of-date and in my repo there is a XXX.97-1 version which is compiled against the recent dav1d :) You can fetch it directly from my repo. But thanks, ldd -r /usr/lib/chromium/chromium will indeed show if there are some broken links, good to know.

danhyal commented on 2019-11-11 14:36

Looking more into it, this might be due to the use of a custom ffmpeg package, on further testing it seems to work just fine with the default ffmpeg and is only an issue when you compile ffmpeg yourself such as in the ffmpeg-full aur package.