Package Details: chromium-ozone 87.0.4280.66-1

Git Clone URL: (read-only, click to copy)
Package Base: chromium-ozone
Description: Chromium built with patches for wayland support via Ozone
Upstream URL:
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: hedgepigdaniel
Maintainer: hedgepigdaniel
Last Packager: hedgepigdaniel
Votes: 27
Popularity: 0.005330
First Submitted: 2019-02-20 22:46
Last Updated: 2020-11-19 21:47

Dependencies (49)

Required by (89)

Sources (3)

Pinned Comments

hedgepigdaniel commented on 2019-11-11 00:06


  • How long does it take to build? Many hours, depending on your system. I recommend enabling ccache in makepkg.conf so that repeated builds are faster.
  • Does VAAPI work? No
  • Are there bugs? Yes, but IMO it's usable. If you want to report bugs, compile with debug symbols in the standard way for arch packages.

Latest Comments

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

lahwaacz commented on 2020-11-27 17:52

Since v87, is there anything that is not provided by the official chromium package?

thotypous commented on 2020-11-24 21:19

Sorry for flagging it incorrectly. Please pin yegorius comment.

yegorius commented on 2020-11-18 01:03

Since v87 Ozone is enabled in official bulds. Just add "--enable-features=UseOzonePlatform --ozone-platform=wayland" to your .config/chromium-flags.conf and enjoy.

hedgepigdaniel commented on 2020-10-12 21:47

Should be fixed. I don't think conflicts will work because that only gets checked on install.

joshuarubin commented on 2020-10-12 18:25

Turns out that I was running gn-git which broke the build. Maybe that should be marked as a conflict (though there is no build-conflict in PKGBUILD)

freswa commented on 2020-10-12 17:36

I'd recommend building in a clean chroot with the devtools. I always build with extra-x86_64-build (also the PKGBUILD below). If you want to build the PKGBUILD available in the AUR repo, you wanna build the ncurses dependency manually and then build chromium-ozone like extra-x86_64-build -- -I ncurses.pkg.tar.zst

joshuarubin commented on 2020-10-12 16:53

I'm getting this when trying to build, any suggestions?:

ERROR at //third_party/blink/renderer/platform/instrumentation/ Dependency not allowed.
source_set("unit_tests") {
The item //third_party/blink/renderer/platform/instrumentation:unit_tests
can not depend on //third_party/blink/renderer/platform:blink_platform_config
because it is not in //third_party/blink/renderer/platform:blink_platform_config's visibility list: [

==> ERROR: A failure occurred in build().

hedgepigdaniel commented on 2020-10-11 11:26

nw. I'm on board with the idea of avoiding custom toolchains, but for these packages (chromium-ozone, chromium-beta-ozone, chromium-dev-ozone), I've opted to accept whatever chromium does as much as possible. That's just because its difficult to get it to build and work otherwise. Although for this package (stable channel) I can copy the patches from the main chromium package, for the beta/dev builds its often just me vs a constant stream of really confusing C++ problems which I don't have the time or skills to solve. So to save time debugging and testing I keep all three channels consistent and wait for others to work out all the weird C++ problems.

Very much excited to have the support in the main package!

freswa commented on 2020-10-11 11:09

Thank you for updating this package. In general we prefer not to use custom toolchains in Arch where possible, so I tried to keep up with the [extra] package as close as possible with my approach.

Hope we can package (optional) ozone support in [extra] soon :)

hedgepigdaniel commented on 2020-10-11 00:16

In the meantime I'm testing a build locally, so once it works (hopefully in about 10 hours) I will update it here.