Package Details: chromium-vaapi 79.0.3945.130-2

Git Clone URL: (read-only, click to copy)
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: 90
Popularity: 3.12
First Submitted: 2016-07-09 09:44
Last Updated: 2020-01-19 00:29

Dependencies (49)

Required by (60)

Sources (14)

Pinned Comments

maximbaz commented on 2019-12-24 19:17

If you are having issues with NVidia, you need to build a patched libva-vdpau-driver-chromium, see here for details.

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 »

maximbaz commented on 2020-01-17 12:10

I'm not familiar with chromium specifics to make this judgement, if you feel that this should be enabled for everyone, let's not limit this to chromium-vaapi only, please propose this for extra/chromium, whether by opening a bug report or contacting maintainer by email (see in PKGBUILD), and in your request explain why this would be beneficial so that it's easier to make the decision :) As soon as it appears in extra/chromium, it will get propagated to this pkg as well.

danhyal commented on 2020-01-15 09:33

@maximbaz I don't think there would be any issues including the flag since you are already depending on freetype, The chromium package 'ungoogled-chromium' also includes the flag and they don't seem to have any issues.

maximbaz commented on 2019-12-24 19:17

If you are having issues with NVidia, you need to build a patched libva-vdpau-driver-chromium, see here for details.

slipknot commented on 2019-12-24 18:24

Just reporting that I have the same problem of the GMA4500 also in HD2000 Sandybridge. Somebody knows what was the last version that worked with intel graphics? I don't have a powerful cpu so compiling times takes a lot, I appreciate any guidance you could give me. Regards.

maximbaz commented on 2019-12-24 13:14

xorgproto removal has been reverted:

@danhyal: I would like to keep this package as close as possible to extra/chromium, and I don't know much about implications of adding use_system_freetype=true, have you considered proposing this to extra/chromium?

DAC324 commented on 2019-12-24 11:37

This package depends on xorgproto being installed. However, the dependency check before the build process does not check if xorgproto is installed.

So it can happen that the build errors out with

ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned non-zero exit code. pkgresult = exec_script(pkg_config_script, args, "value") ^---------- Current dir: /home/gerd/.cache/yay/chromium-vaapi/src/chromium-79.0.3945.88/out/Release/ Command: /usr/bin/python2 /home/gerd/.cache/yay/chromium-vaapi/src/chromium-79.0.3945.88/build/config/linux/ atspi-2 Returned 1. stderr:

Package xproto was not found in the pkg-config search path. Perhaps you should add the directory containing `xproto.pc' to the PKG_CONFIG_PATH environment variable Package 'xproto', required by 'x11', not found Package 'kbproto', required by 'x11', not found Package 'recordproto', required by 'xtst', not found Package 'inputproto', required by 'xi', not found Could not run pkg-config.

See //build/config/linux/atspi2/ whence it was called. pkg_config("atspi2") { ^--------------------- See //content/test/ which caused the file to be included. "//build/config/linux/atspi2", ^---------------------------- ==> ERROR: An error occurred in build(). Aborting... Error making: chromium-vaapi

Fix: sudo pacman -S xorgproto

danhyal commented on 2019-12-24 04:06

Would you consider adding the use_system_freetype=true build flag? It is useful for people using infinality patches for freetype.

slipknot commented on 2019-12-18 18:35

I have a core 2 duo with GMA 4500MHD. With mpv-git vaapi works ok. Installed the last binay from today still got this error:

[28063:28063:1218/] GetConfigAttributes failed for va_profile VAProfileH264ConstrainedBaseline [28063:28063:1218/] GetConfigAttributes failed for va_profile VAProfileH264Main [28063:28063:1218/] GetConfigAttributes failed for va_profile VAProfileH264High [28063:28063:1218/] InitializeSandbox() called with multiple threads in process gpu-process.

VAAPI info: vainfo: VA-API version: 1.5 (libva 2.5.0) vainfo: Driver version: Intel i965 driver for Intel(R) GM45 Express Chipset - 2.3.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD

Kernel: 5.4.2-1-MANJARO #1 SMP PREEMPT Thu Dec 5 09:55:57 UTC 2019 x86_64 GNU/Linux

jmandawg commented on 2019-12-16 20:00

you are right, my bad.

maximbaz commented on 2019-12-16 19:53

I think you meant this comment for chromium-vaapi-bin ;)