Chrome 124.0.6367.60 broke Wayland backend

[blitz]

Describe the bug

The Chrome Wayland backend is broken. Chrome doesn't show a window anymore when --ozone-platform-hint=wayland.

I only have two AMD systems (Zen 2 / Zen 4) with integrated graphics to test this on. Both show this behavior.

Bisecting shows this as the first bad commit (277efb0):

277efb0104e2f6916e12d0a05b035443a1985a5b is the first bad commit
commit 277efb0104e2f6916e12d0a05b035443a1985a5b
Author: emilylange <git@emilylange.de>
Date:   Wed Apr 17 13:16:27 2024 +0200

    chromium: 123.0.6312.122 -> 124.0.6367.60
    
    https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_16.html
    
    This update includes 23 security fixes.
    
    CVEs:
    CVE-2024-3832 CVE-2024-3833 CVE-2024-3914 CVE-2024-3834 CVE-2024-3837
    CVE-2024-3838 CVE-2024-3839 CVE-2024-3840 CVE-2024-3841 CVE-2024-3843
    CVE-2024-3844 CVE-2024-3845 CVE-2024-3846 CVE-2024-3847
    
    (cherry picked from commit 2dd80cf5d28282854550e6eaa4517daa672f24b5)

 .../networking/browsers/chromium/upstream-info.nix           | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

Steps To Reproduce

NIXPKGS_ALLOW_UNFREE=1 nix run --impure .#google-chrome -- --ozone-platform-hint=wayland

Expected behavior

The Wayland backend works.

Notify maintainers

@networkException @emilylange

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.7, NixOS, 23.11 (Tapir), 23.11.20240421.a5e4bbc`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `""`
 - nixpkgs: `not found`

---

Add a 👍 reaction to issues you find important.

[blitz]

Upstream issue: https://issues.chromium.org/issues/329678163

[emilylange]

Duplicate of #306010.

Also please note that we (@networkException and I) do not maintain google-chrome. We maintain chromium.

The only remaining google-chrome maintainer is inactive for all I know.

Yes, google-chrome inherits the version from chromium and we provide hashes for the google-chrome src FOD, but that's usually about it.

I don't particular like the fact google-chrome inherits the version, but this has been decided way before I joined as maintainer and it arguably safes a lot of time.

In a way, its surprising it worked for as long as it did without any issues.

The one exception being 8a3a274.

I think I would prefer to have the versions of google-chrome and chromium independent from one another, but that would need someone, or better a few, to actually maintain google-chrome.

Thanks for the bisect though. That's lovely to see. It usually helps a lot but most don't go the extra mile :)

It's just that we already have another issue tracking this.

[blitz]

@emilylange Thanks for taking the time to explain the situation!