Bug#1121656: (no subject)

[Mauro Sacchetto]

"I wouldn't be surprised if it's a driver-specific wayland bug."

I don't think so for the freeze happens too in Testing (Forky) with 
Cinnamon, obviously with X11.




Il 30/11/25 08:27, Andres Salomon ha scritto:

On 11/30/25 01:54, Mauro Sacchetto wrote:

I've Nvidia card with nouveau drivers, if relevant.

But now all seems works properly if i launch both the browsers 
(Chromium and Google Chrome) from shell with the well known option:


-disable-gpu


I'm assuming that you're using KDE under wayland. If that's the case, 
you could also try the "--ozone-platform=x11" or "--ozone-playform- 
hint=x11" options (without --disable-gpu) to see if that works. I 
wouldn't be surprised if it's a driver-specific wayland bug.

Bug#1121656: (no subject)

[Mauro Sacchetto]

Yes, all latest Debian versions run under Wayland.
Maybe, it'a enough disabilitate graphical acceleration from inside 
Chrome / Chromium settings

I will try your suggestions, thank you

Bug#1121656: (no subject)

[Andres Salomon]

On 11/30/25 01:54, Mauro Sacchetto wrote:

I've Nvidia card with nouveau drivers, if relevant.

But now all seems works properly if i launch both the browsers (Chromium 
and Google Chrome) from shell with the well known option:


-disable-gpu


I'm assuming that you're using KDE under wayland. If that's the case, 
you could also try the "--ozone-platform=x11" or 
"--ozone-playform-hint=x11" options (without --disable-gpu) to see if 
that works. I wouldn't be surprised if it's a driver-specific wayland bug.

Bug#1121656: (no subject)

[Mauro Sacchetto]

I've Nvidia card with nouveau drivers, if relevant.

But now all seems works properly if i launch both the browsers (Chromium 
and Google Chrome) from shell with the well known option:


-disable-gpu