Package Details: chromium-vaapi-bin 70.0.3538.110-1

Git Clone URL: https://aur.archlinux.org/chromium-vaapi-bin.git (read-only)
Package Base: chromium-vaapi-bin
Description: Chromium with VA-API support to enable hardware acceleration, pre-compiled
Upstream URL: https://www.chromium.org/Home
Licenses: BSD
Conflicts: chromium, chromium-vaapi
Provides: chromium, chromium-vaapi
Submitter: maximbaz
Maintainer: maximbaz (OneObsession)
Last Packager: maximbaz
Votes: 54
Popularity: 7.732125
First Submitted: 2017-06-17 14:26
Last Updated: 2018-11-23 21:44

Dependencies (37)

Required by (37)

Sources (1)

Pinned Comments

maximbaz commented on 2018-11-23 23:11

[Announcement] I'm retiring this package in favor of my custom repo for providing pre-compiled chromium-vaapi.

Why: this package suffers from a lack of testing, I'm not actually using it so I often made mistakes, such as submitting wrong hashsums, or uploading a corrupted archive to Github because I was on a mobile network. It makes me sad that I cannot guarantee stable quality.

How to get pre-compiled chromium-vaapi: You can add my repo to your /etc/pacman.conf by adding this to the bottom of the file:

[maximbaz]
Server = https://pkgbuild.com/~maximbaz/repo/

What if I don't want to add your custom repo?:

You have two options really to keep getting pre-compiled chromium-vaapi from me:

  1. Keep an eye on the repo at https://pkgbuild.com/~maximbaz/repo/, download new chromium-vaapi*.pkg.tar.gz files from there and install via pacman -U.

  2. Take over this package and maintain it. Basically all you'd have to do is to switch source from Github to my repo and keep updating version as they are released. I can help with updating PKGBUILD if needed. Because chromium-vaapi in my repo is signed with PGP key, you won't even have to update sha256sums anymore. Let me know.

Latest Comments

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

maximbaz commented on 2018-12-12 09:03

madscience: technically nothing prevents us from doing so, but I personally don't feel confident about moving it, I don't follow chromium development and I understand too little of chromium to make a promise that it will always be working. I also discussed a possibility of just including this VAAPI patch in extra/chromium directly (since it's disabled by default anyway), but maintainer didn't feel like doing so either, he wants to keep chromium as close as possible to the upstream. That's why I simply opened up my repo to the public :)

madscience commented on 2018-12-12 03:18

Is there any chance that this will be promoted to [community]?

digitalone commented on 2018-12-03 12:54

@maximbaz: I'm using you repo. Thanks for your work.

maximbaz commented on 2018-11-23 23:11

[Announcement] I'm retiring this package in favor of my custom repo for providing pre-compiled chromium-vaapi.

Why: this package suffers from a lack of testing, I'm not actually using it so I often made mistakes, such as submitting wrong hashsums, or uploading a corrupted archive to Github because I was on a mobile network. It makes me sad that I cannot guarantee stable quality.

How to get pre-compiled chromium-vaapi: You can add my repo to your /etc/pacman.conf by adding this to the bottom of the file:

[maximbaz]
Server = https://pkgbuild.com/~maximbaz/repo/

What if I don't want to add your custom repo?:

You have two options really to keep getting pre-compiled chromium-vaapi from me:

  1. Keep an eye on the repo at https://pkgbuild.com/~maximbaz/repo/, download new chromium-vaapi*.pkg.tar.gz files from there and install via pacman -U.

  2. Take over this package and maintain it. Basically all you'd have to do is to switch source from Github to my repo and keep updating version as they are released. I can help with updating PKGBUILD if needed. Because chromium-vaapi in my repo is signed with PGP key, you won't even have to update sha256sums anymore. Let me know.

muradm commented on 2018-11-01 09:40

@ForeignCon, yeah figured that out. tried to compile it few days. disgustingly time consuming, gave up after seen that google announcement that they won't support hardware acceleration on linux in any way. and could not find any other browser that does hardware acceleration on linux. suggestions welcome. no happy browsing on Arch.. :)

maximbaz commented on 2018-10-30 22:28

I was talking about icu package in the core repository, chromium-vaapi-bin was compiled against that one (v63). But anyway, it seems you have solved your issue ;)

n.vaughan commented on 2018-10-30 19:47

There isn't at the moment an icu63 AUR package. I used the following PKGBUILD (modified from icu61) to install it: https://pastebin.com/WT4RGmN5

maximbaz commented on 2018-10-30 18:16

Check if your icu package is up to date, latest version is 63. If you are still on 62, either upgrade icu, or downgrade chromium - older versions are available on Github.

Elanzer commented on 2018-10-30 18:09

so we need to do something after the last update?? after building, chromium it's not opening anymore for me. I'm on manjaro by the way, if that matter.

pdf commented on 2018-10-30 06:40

Looks like a rebuild is required for icu v63.x, as the current build is linked against libicui18n.so.62