Package Details: chromium-ozone 73.0.3683.86-4

Git Clone URL: (read-only)
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: 4
Popularity: 1.250254
First Submitted: 2019-02-20 22:46
Last Updated: 2019-05-04 16:58

Dependencies (47)

Required by (46)

Sources (14)

Latest Comments

hedgepigdaniel commented on 2019-05-04 17:02

73.0.3683.86-4 has a fix for the HiDPI scaling bug (

hedgepigdaniel commented on 2019-05-04 17:02

73.0.3683.86-4 has a fix for the HiDPI scaling bug (

alf commented on 2019-04-30 17:18

chromium-algorithm-header.patch did not pass validity check, do you mind to updpkgsums? thank you...

Foreigncon commented on 2019-03-05 06:14

@hedgepigdaniel Hmm. I am going to try building with this patch. It doesn't enable MojoVideo Decoder.

As for as this build is concern, --in-process-gpu breaks the gtk theme, cursor, and hardware acceleration and without it, chromium crashes at start. I am not generating any debugging infos because it takes horrible amount of time to build the package on my machine. But I'm guessing it's because of incomplete mojom wayland implementation. I will let you know if it works.

hedgepigdaniel commented on 2019-03-04 21:57

@ForeignCon no, I haven't been able to get it to work. If you find a way, let me know and I'll update the package. I don't think the Igalia people have turned their attention to hardware decoding yet.

Foreigncon commented on 2019-02-28 17:16

Hi. Is MojoVideoDecoder(vaapi -VDA2) working on Wayland in this build?

hedgepigdaniel commented on 2019-02-26 09:15

The 4x upscaling is a known bug due to a TODO wayland API implementation:

TwainDee commented on 2019-02-24 09:06

This build works pretty well, although I'm not sure why it starts with 4x ui scaling on sway when sway is scaled 2x already on a hidpi display. Seems like they both try to scale and end up scaling too much. And starting with --high-dpi-support=0 --force-device-scale-factor=1 has no effect.

hedgepigdaniel commented on 2019-02-20 23:03

Tip: run with chromium --ozone-platform=wayland --in-process-gpu

The ozone platform is X11 by default, and without --in-process-gpu it crashes almost immediately, at least for me.