Arch Linux User Repository

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.

[5249:5249:1108/155133.900091:ERROR:vaapi_wrapper.cc(497)] GetConfigAttributes failed for va_profile VAProfileH264ConstrainedBaseline [5249:5249:1108/155133.903594:ERROR:vaapi_wrapper.cc(497)] GetConfigAttributes failed for va_profile VAProfileH264Main [5249:5249:1108/155133.903724:ERROR:vaapi_wrapper.cc(497)] 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.

@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 https://pkgbuild.com/~maximbaz/repo/chromium-vaapi-77.0.3865.120-2-x86_64.pkg.tar.xz

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...

@maximbaz Are you aware that your inclusion of vaapi-fix.patch is broken? Please refer to discussion from https://bbs.archlinux.org/viewtopic.php?id=244031. There is a better patch which works for everyone.

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

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

Source links for solution: https://forums.gentoo.org/viewtopic-t-1091016-start-0.html https://bugs.gentoo.org/672778

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

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

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: https://pkgbuild.com/~maximbaz/repo/

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/js_binary.py --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 com.google.javascript.jscomp.parsing.TypeTransformationParser.Keywords.İ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) {

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