Chromium VAAPI

Can we build Chromium with VAAPI for the official repositories? Fedora are distributing Chromium with VAAPI now, and Ubuntu plans to as well via snap. This is the main thing that hinders laptop battery life on Linux, and I'm sure this would be a great benefit to the Tuxedo laptops that ship with Manjaro out of the box.

Is there any reason why this isn't done already? Or is this being talked about?

Manjaros Chromium is imported directly form Arch

See this Bug Report

When Fedora added the patches in their Chromium release, Arch initially tried it out. It wasn't stable enough I suspect, so they reverted the changes.

Has it been tried since, by Arch or the Manjaro team?

Not that I know of. There's a dedicated thread on the Arch Linux Forums: chromium: hardware video acceleration with VA-API

You can also download the binary version from the unofficial archlinuxcn repo here. I do not recommend adding the repo to Manjaro, however.

Yeah, I realise that there's a binary there on that repository, however I don't trust that repo, and yeah there are a bunch of issues adding that repo to Manjaro, like you said. The real solution would be for either Manjaro or Arch to provide it themselves. And seeing as Arch might not do it, I think it might be a good idea for the Manjaro team to revisit this idea.

Its also important to note that as far as I'm aware, that simply building Chromium with "use_vaapi=true" does not enable hardware acceleration by default. It simply allows for it. Advanced users would still have to enable the chrome flag in the "chrome://flags" page to actually enable hardware acceleration.

Is it possible for Manjaro to do this independently of Arch?

It is certainly possible but browsers are a heavy burden on the fairly small group of maintainers. Not only do they take a lot of time/resources to build, but it is important to keep them up-to-date.

Ultimately, it will be up to one of the maintainers if they want to take it on. You will have to wait and see.

It doesn't have to be enabled by default, but there should be a way to obtain a binary from a trusted source. May it be disabled by some in app flags or a separate package.

ungoogled-chromium uses this flag by default.
Would be nice if that browser was adopted.
I'd be willing to build it.


Ah, but that has the same problem as chromium-vaapi, there's no binary available... Also, for me personally, I need Google integration.

Well here you go .. I left this to build while I took a nap...


curl -o chromium-vaapi-83.0.4103.97-1-x86_64.pkg.tar.xz
sudo pacman -U chromium-vaapi-83.0.4103.97-1-x86_64.pkg.tar.xz


curl -o ungoogled-chromium-83.0.4103.97-1-x86_64.pkg.tar.xz
sudo pacman -U ungoogled-chromium-83.0.4103.97-1-x86_64.pkg.tar.xz

@banjo @viggy96 @Schlaefer

1 Like

WOW...beautiful. I am at work now, but will take a nap in about 8 hours.

Alright ... a hundred years later .. here is this:


Just installed one after the other, both working, both have hw-accelleration.
...and where is your coffe box Dude ? :moneybag:
Thank you for your time and energy.

Maybe I'll add that into the site in a sec .. I am going to add ublock origin for chromium

EDIT - ok .. thats done too. I might add some automated builds there too.
Thanks for the thanks :slight_smile:

MK. Double-posting here because I jumped the AUR gun and built chromium-vaapi using the latest release (aur package is flagged out of date) ... anyone using the repo is welcome to let me know if they received the update.

1 Like

At work again, same same, but different. :grin:

Back fine. :100:

Worked here. Looks good. :+1:

1 Like

Forum kindly sponsored by