Bug#1069586: Chromium native Wayland support broken

[Stephan Verbücheln]

Some more tests confirm the following:

--ozone-platform=waylandworks
--ozone-platform-hint=wayland   does not work

Regards
Stephan

Bug#1069586: Chromium native Wayland support broken

[Leandro Cunha]

On Sun, Apr 21, 2024 at 1:27 AM Andres Salomon  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 -> X11works
> > 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 .
>
> 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

Bug#1069586: Chromium native Wayland support broken

[Andres Salomon]

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 -> X11works
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 .


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).




OpenPGP_0x645D0247C36E7637.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069586: Chromium native Wayland support broken

[Stephan Verbücheln]

Workaround:

If you are stuck Chromium using native Wayland support, you can reset
it with the following steps:

1. Log out GNOME on Wayland session and log in with Gnome on Xorg
session.
2. Launch Chromium.
3. Enter chrome://flags into URL bar and reset the setting “Preferred
Ozone platform” to “Default”.
4. Log out and log in again with Wayland session.

Regards
Stephan

Bug#1069586: Chromium native Wayland support broken

[Stephan Verbücheln]

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 -> X11works
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.

I reproduced this with a completely new browser profile.

Regards
Stephan