Package Details: chromium-wayland-vaapi 97.0.4692.99-1

Git Clone URL: https://aur.archlinux.org/chromium-wayland-vaapi.git (read-only, click to copy)
Package Base: chromium-wayland-vaapi
Description: Chromium, patched to enable VA-API video decoding on the Ozone Wayland backend
Upstream URL: https://www.chromium.org/Home
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: hedgepigdaniel
Maintainer: hedgepigdaniel
Last Packager: hedgepigdaniel
Votes: 3
Popularity: 2.11
First Submitted: 2021-11-29 09:16
Last Updated: 2022-01-21 23:08

Dependencies (43)

Required by (95)

Sources (9)

Pinned Comments

hedgepigdaniel commented on 2021-12-01 11:40

FAQ
How long does it take to build

A really long time

What GPU does it work on

I've tested successfully on:

  • Intel, using intel-media-driver
  • AMD (RX 5600XT)
How can I test that it's working

Go to the media tab in the devtools, and look for VdaVideoDecoder.

What flags do I need

This is an example of a set of flags that does work:

--enable-features=UseOzonePlatform
--ozone-platform=wayland

--ignore-gpu-blocklist
--enable-gpu-rasterization
--enable-zero-copy

--disable-gpu-driver-bug-workarounds

--enable-accelerated-video-decode
--enable-features=VaapiVideoDecoder

Latest Comments

hedgepigdaniel commented on 2022-01-21 12:01

@wooque no I haven't I'd be surprised if they included it because its only a draft at this point, and VA-API on Wayland is planned to be supported in upstream eventually.

dedguy21 commented on 2022-01-18 11:14

I got the following error during build:

[40502/50251] ACTION //v8:run_gen-regexp-special-case(//build/toolchain/linux/unbundle:default)
FAILED: gen/v8/src/regexp/special-case.cc 
python3 ../../v8/tools/run.py ./gen-regexp-special-case gen/v8/src/regexp/special-case.cc terminate called after throwing an instance of 'std::system_error'
what():  Unknown error -1
Return code is -6
[40511/50251] LINK ./torque
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting..

cbix commented on 2021-12-30 14:25

Same issue as @Echo2124 here. For some reason the created toolchain binaries (like flatc and protoc) are broken. I found this thread and it seems to be caused by some default CFLAGS in a newer makepkg.conf. These should either be removed or overwritten by a fixed CFLAGS/CXXFLAGS in the PKGBUILD:

  # prevent SIGTRAP
  CFLAGS=${CFLAGS/-fexceptions}
  CFLAGS=${CFLAGS/-fcf-protection}
  CXXFLAGS="$CFLAGS"

  # ... more CFLAGS ...

The reason this problem doesn't occur for some people is because probably they would still have the old /etc/makepkg.conf and never applied the changes from the /etc/makepkg.conf.pacnew.

So far it seems to work well with the chromium-flags mentioned in FAQ and h264ify. Only got one page crash/segfault, gotta watch how stable this build is.

Echo2124 commented on 2021-12-27 16:53

Hi there was trying to build this, however I got this error looking up the error I was unable to come to a solution. Is anyone else having this problem? Seems to be a build issue:

[5609/50251] ACTION //extensions/browser/api/declarative_net_request/flat:extension_ruleset_gen(//build/toolchain/linux/unbundle:default) FAILED: gen/extensions/browser/api/declarative_net_request/flat/extension_ruleset_generated.h python3 ../../build/gn_run_binary.py flatc -c --keep-prefix -o gen/extensions/browser/api/declarative_net_request/flat -I ../../ ../../extensions/browser/api/declarative_net_request/flat/extension_ruleset.fbs flatc failed with exit code -5 [5622/50251] ACTION //third_party/blink/renderer/bindings:generate_bindings_all(//build/toolchain/linux/unbundle:default) ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting...

wooque commented on 2021-12-05 19:37

Did you try to contact maintainer of official chromium to add Wayland VAAPI patch?

hedgepigdaniel commented on 2021-12-01 11:40

FAQ
How long does it take to build

A really long time

What GPU does it work on

I've tested successfully on:

  • Intel, using intel-media-driver
  • AMD (RX 5600XT)
How can I test that it's working

Go to the media tab in the devtools, and look for VdaVideoDecoder.

What flags do I need

This is an example of a set of flags that does work:

--enable-features=UseOzonePlatform
--ozone-platform=wayland

--ignore-gpu-blocklist
--enable-gpu-rasterization
--enable-zero-copy

--disable-gpu-driver-bug-workarounds

--enable-accelerated-video-decode
--enable-features=VaapiVideoDecoder