Package Details: chromium-vaapi 87.0.4280.88-1

Git Clone URL: https://aur.archlinux.org/chromium-vaapi.git (read-only, click to copy)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
Upstream URL: https://www.chromium.org/Home
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (felixonmars, liewkj)
Last Packager: liewkj
Votes: 116
Popularity: 1.21
First Submitted: 2016-07-09 09:44
Last Updated: 2020-12-03 22:02

Dependencies (50)

Required by (73)

Sources (5)

Pinned Comments

liewkj commented on 2020-08-28 06:04

For NVIDIA or X.Org session, use --use-gl=desktop. For Intel/AMD and Wayland session, use --use-gl=egl.

Wayland session with EGL backend requires patched mesa that supports ANGLE_sync_control_rate.

liewkj commented on 2020-06-28 21:41

Precompiled unsigned binary package available at openSUSE Build Service repositories. Use at your own risk.

https://download.opensuse.org/repositories/home:/kjliew/Arch/x86_64/

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.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

vova7890 commented on 2020-11-28 00:36

==> Starting build()... make: Entering directory '/media/hdd/home/vova7890/Sources/chromium-vaapi/src/chromium-launcher-6' cc -o chromium -D_FORTIFY_SOURCE=2 -DLAUNCHER_VERSION=\"v6\" -DCHROMIUM_NAME=\"chromium\" -DCHROMIUM_BINARY=\"/usr/lib/chromium/chromium\" -DCHROMIUM_VENDOR="\"Arch Linux\"" -DPEPPER_FLASH_DIR=\"/usr/lib/PepperFlash\" -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/json-glib-1.0 -pthread -I/usr/include/libmount -I/usr/include/blkid -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now launcher.c -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 make: Leaving directory '/media/hdd/home/vova7890/Sources/chromium-vaapi/src/chromium-launcher-6' ERROR at //chrome/test/chromedriver/BUILD.gn:16:1: set_sources_assignment_filter argument must be an empty list. set_sources_assignment_filter(deprecated_default_sources_assignment_filter) ^------------------------------------------------------------------------- See //BUILD.gn:115:7: which caused the file to be included. "//chrome/test/chromedriver:chromedriver_unittests", ^-------------------------------------------------- ==> ERROR: A failure occurred in build(). Aborting...

I am the only one with this problem?!

RESOLVED invalid version of "gn"

solopasha commented on 2020-11-25 10:51

@unknown78, same here, I guess vp9 decoding is broken in 87. In 86 worked like a charm with libva-vdpau-driver-vp9-git

DAC324 commented on 2020-11-24 08:48

@unknown78 @gardotd426

I am running version 87 with the nvidia driver 390.132 on kernel 5.9.10 here without problems.

My ~/.config/chromium-flags.conf:

--use-gl=desktop
--ignore-gpu-blocklist
--enable-gpu-compositing
--enable-gpu-rasterization
--enable-native-gpu-memory-buffers
--enable-oop-rasterization
--enable-zero-copy
--disable-gpu-driver-bug-workarounds
--disable-gpu-driver-workarounds
--disable-font-subpixel-positioning
--enable-accelerated-video-decode

liewkj commented on 2020-11-24 05:46

@unknown86 @gardotd426 No problem with VA-API on NVIDIA with 390xx for version 87, but my old GPU only supports H.264. It is probably NVIDIA latest Linux driver or libva-vdpau-* but I have no way to test them. I just did a complete update to kernel 5.9.10.

gardotd426 commented on 2020-11-23 01:01

@unknown78 this is a known issue, idk what the problem is but it starts with version 87.

You can use regular chromium version 86 and it will work.

You don't need this package, hw acceleration w/ Nvidia works on the regular chromium package, but after installing you'll have to downgrade to version 86 because it's broken on 87 (both the chromium and chromium-vaapi packages).

You can do this easily by installing downgrade. Just install chromium, then install downgrade, then run sudo downgrade chromium and select version 86.

unknown78 commented on 2020-11-22 23:29

Hi guys, i can't get accelartion to run with nvidia.

I get the following error:

Failed to create dedicated X11 display!
[166391:166768:1123/002603.454219:ERROR:vaapi_utils.cc(47)] vaMapBuffer failed: invalid VABufferID
[166391:166768:1123/002603.454298:ERROR:vaapi_video_decode_accelerator.cc(528)] Error decoding stream
[166655:24:1123/002603.459559:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"VDA Error 4"}
[166655:24:1123/002603.459653:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"video decode error!"}
[166655:1:1123/002603.459766:ERROR:batching_media_log.cc(35)] MediaEvent: {"pipeline_error":3}
[166391:166391:1123/002603.479844:ERROR:shared_context_state.cc(74)] Skia shader compilation error

cat ~/.config/chromium-flags.conf
--use-gl=desktop
--enable-zero-copy
--disable-frame-rate-limit
--disable-gpu-vsync

gardotd426 commented on 2020-11-05 13:33

@DAC324 you have to click the one that says "KPlay."

It will only be there if something is actively playing (not paused).

DAC324 commented on 2020-11-05 10:54

For me, chrome://media-internals/ does not show anything like MojoDecoder or FFMPEGVideoDecoder. All I get is a bunch of KWebMediaPlayerDestroyed entries.

There is also no video_decoder field as described in the Arch Wiki.

It looks like at least in some Chromium versions, this information is not present in chrome://media-internals/ anymore.

What you have to do is the following: 1. Open a page with a video to be played (e.g., YouTube), and start playback. 2. Press CTRL+Shift+I to open Developer Tools. 3. In the upper window, select the Media Tab. 4. Check the Video Decoder entry there.

gardotd426 commented on 2020-11-04 13:47

@DAC324 Lol it takes hours (multiple) even with an 8-core Zen 2 CPU, so it's not a quick build for anyone unless you maybe have a 3990X or something.

@LinX you can't use hw-accel without --use-gl=desktop, so there's not really anything that can be done.

Also, chromium 86 from the official repos does indeed use hardware acceleration on both AMD and Nvidia, so unless you're on Intel or something it shouldn't be showing FFMpegVideoDecoder.

gardotd426 commented on 2020-11-04 13:47

@DAC324 Lol it takes hours (multiple) even with an 8-core Zen 2 CPU, so it's not a quick build for anyone unless you maybe have a 3990X or something.

@LinX you can't use hw-accel without --use-gl=desktop, so there's not really anything that can be done.

Also, chromium 86 from the official repos does indeed use hardware acceleration on both AMD and Nvidia, so unless you're on Intel or something it shouldn't be showing FFMpegVideoDecoder.