On Sun, Apr 21, 2024 at 1:27 AM Andres Salomon <dilin...@queued.net> wrote: > > Control: tags -1 forwarded https://crbug.com/329678163 > Control: severity -1 serious > > On 4/20/24 23:13, Stephan Verbücheln wrote: > > Package: chromium > > Version: 124.0.6367.60-1~deb12u1 > > > > Since the last update, Chromium does work with native Wayland. It is > > starting up, but it is displaying an invisible window. It is listed in > > the window switchers (Alt+Tab), Gnome Shell etc., but invisible. > > > > Note: The default configuration uses X11 via XWayland and is working. > > > > The setting can be managed via command line arguments or by typing > > chrome://flags into the URL bar (filter for ozone). > > > > Available settings: > > default -> X11 works > > auto -> Wayland if available does not work > > x11 works > > wayland does not work > > > > I have been using Chromium with native Wayland for many months without > > problems until the last update. > > > > Thanks for the heads up. Seems like this is v124-specific, and reported > upstream at <https://crbug.com/329678163>. > > If they don't fix it in the stable channel, I'll backport a fix. In the > meantime it does seem like you can get it work in wayland mode using > command-line args, according to that bug report thread, though I haven't > tested it myself (I'm on X11 here). >
Very interesting, using GNOME under Wayland with Intel hardware with no apparent problems. Remembering that I use unstable. -- Cheers, Leandro Cunha
