Google Chrome 124.0.6356.2-1 break --ozone-platform=wayland

[gptlang]

OS/Platform

Fedora and CentOS

Installed

Flatpak

Version

Chromium 124.0.6367.60

Have you tested that this is not an upstream issue or an issue with your configuration?

• I have tried reproducing this issue in Chrome and it could not be reproduced there
• I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
• I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

The window is transparent and cannot be interacted with

How to Reproduce?

1. flatpak install io.github.ungoogled_software.ungoogled_chromium
2. flatpak run io.github.ungoogled_software.ungoogled_chromium

Actual behaviour

A transparent window

Expected behaviour

A working window

Relevant log output

[2:2:0423/212753.846306:ERROR:chrome_browser_cloud_management_controller.cc(161)] Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build.
[2:2:0423/212754.228053:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.UnknownMethod: Unknown method GetActive or interface org.freedesktop.ScreenSaver.

[gptlang]

Downgraded to 14d2449cf95d2d9ef4977e1dc1eb83ab3a1219636305a2878c1a2fbc08aacf98 and that has proven to work

Edit: Verified that every commit before (but not including) 28ba519d6e615e61281895dc718fa196c7e7b13fce9140c918fbe12618738083 works

Edit 2: Also note that the log output is consistent across commits. There are no additional error messages that hint as to why it doesn't render

[rany2]

Do you have any Wayland flags set?

[networkException]

This is a known upstream issue: https://issues.chromium.org/issues/329678163

People reported that explicitly specifying --ozone-platform=wayland works (see NixOS/nixpkgs#306010 (comment))

[flightmansam]

flathub/com.github.Eloston.UngoogledChromium#24 (comment)

Running this fixed the issue

[acheong08]

Seems like this just got fixed upstream: https://chromium-review.googlesource.com/c/chromium/src/+/5474983

[rany2]

This issue could be closed, the Flatpak has a fix backported.