Package Details: chromium-vaapi 88.0.4324.182-1

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 (felixonmars, liewkj)
Last Packager: liewkj
Votes: 114
Popularity: 0.22
First Submitted: 2016-07-09 09:44
Last Updated: 2021-02-19 19:21

Dependencies (48)

Required by (87)

Sources (6)

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.

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 »

Gonzo2028 commented on 2021-01-16 18:26

Does not build for me.

../../third_party/abseil-cpp/absl/synchronization/internal/ error: no member named 'numeric_limits' in namespace 'std' if (x->version == std::numeric_limits<uint32_t>::max()) { ~~~~~^ ../../third_party/abseil-cpp/absl/synchronization/internal/ error: unexpected type name 'uint32_t': expected expression if (x->version == std::numeric_limits<uint32_t>::max()) { ^ ../../third_party/abseil-cpp/absl/synchronization/internal/ error: no member named 'max' in the global namespace if (x->version == std::numeric_limits<uint32_t>::max()) { ~~^ 3 errors generated. [2721/42997] ACTION //chrome/browser/...ild/toolchain/linux/unbundle:default) ninja: build stopped: subcommand failed.

liewkj commented on 2021-01-03 21:58

I confirmed that intel-media-driver failed video decode acceleration with Wayland/EGL. No idea what was going on. X11 and --use-gl=desktop is fine.

[3210:3210:0103/] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[3210:3210:0103/] Failed creating VASurface for NativePixmap
[3210:3210:0103/] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[3210:3210:0103/] Failed creating VASurface for NativePixmap
[3402:12:0103/] MediaEvent: {"error":"VDA Error 4"}

blispx commented on 2021-01-02 23:22

Strange, on intel-media-driver 20-4.1 works fine, on 20-4.3 checkerboard, on 20-4.5 hardware acceleration doesn't work under egl

@liewkj do you know what's going on?

gardotd426 commented on 2020-12-29 01:32

Well the thing is, downgrading chromium doesn't require downgrading icu. And even if it did, it wouldn't matter because thunderbird works with versions of icu going all the way back to 64.

I've done the very thing I suggested to you (before I just said screw it and gave up on always-on hw acceleration for now), and there should be no issues whatsoever just downgrading chromium. You don't have to downgrade anything else.

You literally just run sudo downgrade chromium, select the version you want to move to, and that's it.

But yeah, if for some weird reason that's not acceptable to you, then just use the current chromium package with h264ify and just deal with only 1080p h264 decoding. The thing is, I doubt your GPU is capable of anything beyond that anyway.

Either way, there's no need for you to use this package, as vaapi is enabled in the official chromium package, as I said.

talessx commented on 2020-12-28 18:27

Ok, thanks a lot for these very usefull informations. It's not very easy to downgrade as dependencies like libicui (icu) are linked to other software like Thunderbird. Anyware now I'm more aware about the problem and hope next versions of either chromium or libva-vdpau-driver-vp9-git solve the problem. Let's not get angry it's a wonderful penguin world! Let's hope this climate changes do not make appear a crack in the thin ice under its feet..(yes in the modern life)..! It's very important this info exchange between us. So thanks a lot for your help and sorry for my english. ale

gardotd426 commented on 2020-12-23 16:21

Lmao LITERALLY THE LINK YOU GAVE says "86 builds work fine." Literally what I've been saying.

Dude, install chromium from the official repos. Then install libva-vdpau-driver-vp9-git and the package called downgrade. Then run sudo downgrade chromium and choose version 86. You'll have working hardware acceleration, and if you don't, it's because your legacy drivers are incapable. Because even as your own sources state, version 86 WORKS with 20 series, 30 series, and 10 series.

gardotd426 commented on 2020-12-23 16:19

You're really, really failing to grasp this, huh.

As I've said, explicitly, numerous times, VP9 IS BROKEN ON 87.

Those people complaining you're linking to? They're talking about THIS VERY BUILD! chromium-vaapi. They're not talking about the official Arch package.

This also has nothing to do with chromium. It's the libva-vdpau-driver-vp9-git that's broken, and libva-vdpau-driver-chromium has no vp9 acceleration, only h264.

I've literally stated numerous times on this thread that in v87, things aren't working correctly, and only h264 works, and you need h264ify to force it. But in version 86, of the OFFICIAL chromium package in the Arch repos, BOTH h264 and vp9 work. Which is the original point you tried to dispute.

So now you're literally making the exact same points I've already made numerous times in this thread, to try and argue against a completely separate point. I don't know what's up with your reading comprehension, but it's ridiculous.

On BOTH chromium from the official Arch repos and chromium-vaapi from the AUR, hw acceleration does NOT work with libva-vdpau-driver-vp9-git on v87. It DOES work (on BOTH chromium and chromium-vaapi) with libva-vdpau-driver-chromium and h264ify. On v86, on BOTH chromium and chromium-vaapi, both work.

That's literally what I've been saying this entire time.

DAC324 commented on 2020-12-23 16:11

Other people are also saying "it does not work on nvidia":

There are similar complaints aswell if you google for No hardware acceleration for Nvidia-Cards (vdpau) using 87. builds of chromium - and I am pretty sure that not all of these people are using legacy cards.

So it looks like that problem is not solved in general.

Again - apologies for sounding rude but it looks like you cannot be convinced that it works just because you are satisfied with your particular setup. Other people's mileage, unfortunately, varies - including mine:

gardotd426 commented on 2020-12-23 15:55

Well you were definitely rude.

You tried and call me out and say I was wrong and that "it doesn't work on Nvidia" despite the fact that YOU'RE USING LEGACY DRIVERS. You're not even using a modern Nvidia card. So why on earth would you even assume that your experience is typical?

And as far as chromium vs chromium-vaapi, you're almost certainly not going to have any different experience using chromium-vaapi, because as I said, the official chromium package is already built with vaapi support. So this package will not be any different.

You can try, but it's unlikely to fare much better for you.

And as for people on current Nvidia GPUs running current drivers, the regular chromium package is in fact the same as this, both allow h264 acceleration (but vp9 is broken regardless on v87, it works on v86).

DAC324 commented on 2020-12-23 15:17

@gardotd426: I didn't want to be rude - But I must admit that I am not a friend of the famous American smalltalk, either. I'd just like to go straight to the point.

And in fact, it looks like Chromium VAAPI does not work very well with at least older nVidia cards necessitating driver version 390 and lower.

Please see screenshots:

Every time I try to play a h.264 video, I get that garbled output unless I disable accelerated-video-decode. Following the recommendation, I had installed chromium from the repo. Looks like I will have to try chromium-vaapi again.

UPDATE: It happens with Chromium-Vaapi as well. Fun fact: It seems to ignore my ~/.config/chromium-flags.conf as I have --enable-accelerated-video-decode set there but the setting remains disabled within Chromium. I must enable it in chrome://flags.

As I was assuming that setting --enable-accelerated-video-decode should indeed enable accelerated video decode, I apparently was overlooking that behavior.

As for your several hints - Thank you very much for your efforts trying to help.

I have amended all the flags but,of course,to no avail. Looks like Chromium is ignoring the chromium-flags.conf file whatsoever.

h264ify is installed and enabled at all places.

libva-vdpau-driver-chromium 0.7.4-7 is installed.