Package Details: chromium-ozone 83.0.4103.116-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: 21
Popularity: 1.55
First Submitted: 2019-02-20 22:46
Last Updated: 2020-06-27 06:07

Dependencies (47)

Required by (69)

Sources (5)

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 »

muzi commented on 2020-06-25 02:33

[BUG] The fcitx and iBus input method can't active in chromium-ozone, but they work normally in other wayland application.

horst commented on 2020-06-20 20:50

I borrowed another computer to try to build it. An older Dell workstation with an Intel Xeon X5650 (32 nm, 6 cores, 12 threads, 2.66 GHz, 12 MB cache), 32 GB RAM and a 1 TB, 7200 RPM spinning hard drive. It took 5 hours 28 minutes to compile and link. I estimate it took about 1 kW of energy. I would not do it again on this machine or anything slower or less efficient.

@tsujp Thank you for the numbers. You motivated me to try on a better computer. That Ryzen seems very capable.

hussam commented on 2020-06-13 11:28

Any prebuilt packages?

hedgepigdaniel commented on 2020-06-02 08:37

The real reason I maintain these packages is to warm up the house in winter.

tsujp commented on 2020-06-02 08:31

@horst I compiled this on a Ryzen 3700x with 32 GB of memory and it took about 1-2 hours if I were to spitball. I didn't time it exactly but it was a long time.

horst commented on 2020-06-01 10:41

How long does the compilation of this take on an average computer? On my i3 with 8 GB RAM it took more than 10 hours to compile around 29xxx of the 39xxx files before I had to abort it. This seems way off compared with some older compilation benchmarks I can find for Chromium where even lesser hardware can do multiple builds per day.

jtheoof commented on 2020-05-30 21:16

I simply took the PKGBUILD from chromium official package maintainer and added the wayland required compile flags. It works well:

I would be happy to maintain this package @hedgepigdaniel if you want.

horst commented on 2020-05-30 13:15

@jtheoof Are the changes inside chromium-83-gcc-10.patch not already in the upstream chromium-81.0.4044.138.tar.xz? I get this when I add chromium-83-gcc-10.patch to the PKGBUILD and run makepkg:

jtheoof commented on 2020-05-22 09:18

@kneel Your compiling issues have to do with the gcc 10 updates. Even chromium would not compile without the gcc 10 patches. Chromium maintainer recently added those, so the maintainer of this package would have to do the same:

kneel commented on 2020-05-19 19:57

So far I have been unable to build this.. First issue I encountered was this: I was able to solve issue by adding #include <string> in the /base/trace_event/trace_event_memory_overhead.h file in the chromium extract directory. But after this, I am still getting more issues. More stdint declaration issues but currently a lot of unterminated conditional directive errors: I included several chromium 81 patches from in my PKGBUILD but they did not solve any issues :/

Not sure if it's an issue with my compiler or what- The most useful info I have found on the issue is here:

Any help would be greatly appreciated! Thanks!