Background
PR #2506 changes the default Chromium backend in our .desktop entries from --ozone-platform=x11 to not providing it. On a Wayland session this means the app runs as a native Wayland client by default instead of being forced onto XWayland.
The X11 force was added in 2.7.4 to mask widespread Electron 38 era Wayland regressions. Electron 41 has shipped meaningful Ozone/Wayland improvements since then, and several reporters have independently validated that --ozone-platform=wayland or not providing this works correctly for them now. This is the moment to retest whether we don't need to force x11 anymore.
What I am asking
I want to ship this default for the next release, but I need as many testers as possible across different setups before I am comfortable. Both "everything still works" and "this regressed" reports are equally valuable. The more compositor, GPU, and packaging combinations I hear back on, the more confident the call is.
How to test
Grab the PR build that matches your install. Both URLs stay current as new commits land on the PR:
Launch from the application menu rather than a terminal. The terminal launch path does not pick up the .desktop default flags, so testing from the menu is what reflects the actual default for stock users.
Areas I would like covered
Screen sharing on Wayland (especially on hybrid GPU laptops), maximize and focus-loss behaviour on Wayland, crashes during calls under GNOME Wayland, appTitle / appIcon / awayOnSystemIdle on Wayland, fractional scaling on Wayland, and anything else that worked on 2.8.x but stops working with this build.
What to report
A short comment with: distro and version, display server (Wayland or X11) and compositor, GPU vendor and driver, package format, what worked or regressed, and whether passing --ozone-platform=x11 manually restores anything that broke.
Thanks!
Background
PR #2506 changes the default Chromium backend in our
.desktopentries from--ozone-platform=x11to not providing it. On a Wayland session this means the app runs as a native Wayland client by default instead of being forced onto XWayland.The X11 force was added in 2.7.4 to mask widespread Electron 38 era Wayland regressions. Electron 41 has shipped meaningful Ozone/Wayland improvements since then, and several reporters have independently validated that
--ozone-platform=waylandor not providing this works correctly for them now. This is the moment to retest whether we don't need to force x11 anymore.What I am asking
I want to ship this default for the next release, but I need as many testers as possible across different setups before I am comfortable. Both "everything still works" and "this regressed" reports are equally valuable. The more compositor, GPU, and packaging combinations I hear back on, the more confident the call is.
How to test
Grab the PR build that matches your install. Both URLs stay current as new commits land on the PR:
Launch from the application menu rather than a terminal. The terminal launch path does not pick up the
.desktopdefault flags, so testing from the menu is what reflects the actual default for stock users.Areas I would like covered
Screen sharing on Wayland (especially on hybrid GPU laptops), maximize and focus-loss behaviour on Wayland, crashes during calls under GNOME Wayland, appTitle / appIcon / awayOnSystemIdle on Wayland, fractional scaling on Wayland, and anything else that worked on 2.8.x but stops working with this build.
What to report
A short comment with: distro and version, display server (Wayland or X11) and compositor, GPU vendor and driver, package format, what worked or regressed, and whether passing
--ozone-platform=x11manually restores anything that broke.Thanks!