Package Details: chromium-vaapi 78.0.3904.97-1

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: 86
Popularity: 3.67
First Submitted: 2016-07-09 09:44
Last Updated: 2019-11-10 11:56

Dependencies (48)

Required by (54)

Sources (12)

Pinned Comments

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 »

agm28011997 commented on 2019-11-08 14:57

[5249:5249:1108/] GetConfigAttributes failed for va_profile VAProfileH264ConstrainedBaseline [5249:5249:1108/] GetConfigAttributes failed for va_profile VAProfileH264Main [5249:5249:1108/] GetConfigAttributes failed for va_profile VAProfileH264High

I am getting those errors when lauching chromium vaapi in a intel core 2 duo PC with GMA. chromium had vaapi acceleration a few versions ago, I don't know why is not working now, but with mpv vaapi works well and in other laptops chromium vaapi is working good too.

maximbaz commented on 2019-10-14 23:18

@freefreeno maybe you are out of space? But if you are OK using the -bin package and are looking for a quick workaround, feel free to just install the pkg directly from the repo like so:

sudo pacman -U

freefreeno commented on 2019-10-14 23:03

Why would I be getting this erros with trying to uild this package. I normally use the bin but today it is failing to download then I get this when trying to manually build this package.

RROR: Failed to extract chromium-77.0.3865.120.tar.xz Aborting...

liewkj commented on 2019-10-11 23:06

@maximbaz Are you aware that your inclusion of vaapi-fix.patch is broken? Please refer to discussion from There is a better patch which works for everyone.

toki1990 commented on 2019-09-23 01:16

Note: I tried lots of opendjk/jre or oracle java version. Not solution.

toki1990 commented on 2019-09-23 01:14

I found a solution for compile. Problem may be related with my software configuration or hardware.

Source links for solution:

I'm added 'closure_compile=false' to local flags.

toki1990 commented on 2019-09-22 21:27

Thanks for fast replies. Same error message different step. I can use precompiled version.

maximbaz commented on 2019-09-22 21:13

Oh so it fails on different step every time? I wonder if it's possible that you are running out of resources and that's why the build crashes?

As a potential workaround, feel free to grab the compiled version from my repo:

toki1990 commented on 2019-09-22 21:10

Third try: (problem may be related to my system)

[3309/35953] ACTION //mojo/public/js:bindings_lite(//build/toolchain/linux/unbundle:default) FAILED: gen/mojo/public/js/mojo_bindings_lite.js /usr/bin/python2 ../../third_party/closure_compiler/ --compiler ../../third_party/closure_compiler/compiler/compiler.jar --output gen/mojo/public/js/mojo_bindings_lite.js --deps gen/mojo/public/js/bindings_lite_sources.js_library --sources ../../mojo/public/js/bindings_lite.js --flags jscomp_error=accessControls jscomp_error=ambiguousFunctionDecl jscomp_error=checkTypes jscomp_error=checkVars jscomp_error=constantProperty jscomp_error=deprecated jscomp_error=externsValidation jscomp_error=globalThis jscomp_error=invalidCasts jscomp_error=misplacedTypeAnnotation jscomp_error=missingProperties jscomp_error=missingReturn jscomp_error=nonStandardJsDocs jscomp_error=suspiciousCode jscomp_error=undefinedNames jscomp_error=undefinedVars jscomp_error=unknownDefines jscomp_error=uselessCode jscomp_error=visibility compilation_level=ADVANCED_OPTIMIZATIONS language_in=ECMASCRIPT_2017 language_out=ECMASCRIPT5_STRICT generate_exports --externs ../../third_party/closure_compiler/externs/chrome.js ../../third_party/closure_compiler/externs/polymer-1.0.js ../../third_party/closure_compiler/externs/mojo_core.js ../../third_party/closure_compiler/externs/pending.js java.lang.RuntimeException: INTERNAL COMPILER ERROR. Please report this problem.

No enum constantİSUNKNOWN Node(FUNCTION ): [synthetic:es6/promise/promise] :390:36 PolyfillPromise.prototype.catch = function(onRejected) { Parent(ASSIGN): [synthetic:es6/promise/promise] :390:2 PolyfillPromise.prototype.catch = function(onRejected) {

maximbaz commented on 2019-09-22 20:18

I pushed to AUR only after I successfully compiled it in chroot, maybe this is a transient error, could you try again?