Google Chrome and Chromium 124 have a transparent window on Wayland

[Achim Behrens]

chromium snap only launches with titlebar and transparent window after recent snap update on wayland and intel grafics.

Adding --ozone-platform=wayland fixes the issue for me. (workaround from bug #1968610)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: chromium-browser 2:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Sun Apr 21 20:25:30 2024
DiskUsage:
 Filesystem Type Size Used Avail Use% Mounted on
 rpool/ROOT/ubuntu_gk6kaa zfs 50G 7,7G 42G 16% /
 tmpfs tmpfs 16G 128M 16G 1% /dev/shm
 rpool/USERDATA/k1l_0tberh zfs 437G 396G 42G 91% /home/k1l
InstallationDate: Installed on 2022-03-24 (760 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
Snap.Changes:
 ID Status Spawn Ready Summary
 635 Done 2024-04-21T00:51:33+02:00 2024-04-21T00:52:11+02:00 Snap "chromium" aktualisieren
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60 (8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Tracking upstream in:
https://issues.chromium.org/issues/329678163

[Daniel van Vugt (vanvugt)]

Looks like the fix is in Chrome 124.0.6367.118

[Guido Jakobs (guidojakobs)]

I'm running 22.04LTS on an AMD 4700U with Wayland and I experience the same result when starting Chromium Snap 124.0.6367.91.
A transparent/glitching window opens without seeing the actual browser.
When reverting to Chromium Snap 123.0.6312.58 I can use the browser again.

[Nathan Teodosio (nteodosio)]

Any luck with 124.0.6367.118?

[Achim Behrens (k1l)]

fixed with todays update chromium 124.0.6367.118