Package Details: chromium-vaapi 75.0.3770.90-3

Git Clone URL: (read-only)
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: 71
Popularity: 6.229244
First Submitted: 2016-07-09 09:44
Last Updated: 2019-06-18 11:51

Dependencies (48)

Required by (47)

Sources (10)

olive commented on 2016-11-17 11:23

I want to try this version, but according to this:

the hardware requirement for the build is high, to say the least. Maybe, it could be worthwhile to offer a precompiled binary in addition to the source. I don't think the majority of Archlinux users have that. Or maybe it is possible to build chromium with a more reasonable amount of memory?

samcv commented on 2016-11-17 00:09

How would people feel if I just jumped to 55 before it has been officially released? Thoughts? Seems there may be more issues staying on 53 than I'd thought.

ccb23 commented on 2016-11-16 13:51

Looks like this version (53.0.2785.143-1) is affected by the NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED issue.

As far as I understand, its build timestamp may not be older than 10 weeks?!

Maybe you could update (just rebuild) the binary package...

Blind55 commented on 2016-11-15 15:49

I have modified the current chromium VAAPI patch for debian at github (that is a patch that operates on 55). The key to make that patch work, I believe, is to adjust the path to the libraries. I got it to work on the iridium 54 browser (I think):
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0

lrusak commented on 2016-11-10 20:29

What is the reason that it will work in 55 but not in 54?

Also, do you have a 55 build and/or sources?

samcv commented on 2016-11-10 17:02

Also an update to anybody reading. This package will be updated when 55 comes out. 54 does not work with VA-API on Linux but 55 should, so for now use my prebuilt packages. Thanks dustovich. Must have been some package chromium depends on that got updated and caused it to not build properly anymore :(

dustovich commented on 2016-11-10 16:59

Once this package is updated to the latest version this should be solved.

Dheart commented on 2016-11-01 09:06

I would think it's a dependency issue, as in having something installed on your system, which we don't...

FAILED: obj/printing/backend/printing.print_backend_cups.o
../../printing/backend/ In member function ‘base::FilePath printing::PrintBackendCUPS::GetPPD(const char*)’:
../../printing/backend/ error: ‘cupsGetPPD’ was not declared in this scope
ppd_file_path = cupsGetPPD(name);
../../printing/backend/ error: ‘cupsGetPPD2’ was not declared in this scope
ppd_file_path = cupsGetPPD2(http.http(), name);
[20/10072] ACTION nacl_helper_nonsfi: bui...-32 nexe_a45e65dd2094118c61f49edd75dfc172
ninja: build stopped: subcommand failed.

samcv commented on 2016-10-28 19:00

Hmm I'm not sure what would be causing that compilation error. You can always try running "makepkg --noextract" to try and resume the compilation from where it was before. The patch doesn't touch those files so I'm not sure what could be causing that.

Dheart commented on 2016-10-28 14:23

I also can't build with the same error as aphirst