Bug#1121656: Chromium freezes on Stable with kde-plasma-destop
On 11/30/25 09:42, Riku Voipio wrote: > 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. This appears indeed the the case debian stable (nouveau driver and kde wayland) Starting chromium without arguments hangs Starting chromium with --disable-gpu works Starting chromium with --ozone-platform=x11 works Probably same issue as reported on upstream: https://issues.chromium.org/issues/445738043 "Chrome does not provide support for nouveau driver due to stability, nvidia proprietary driver might be stabler(ish)." Ugh. Upstream's attitude towards everything wayland continues to disappoint.
Bug#1121656: Chromium freezes on Stable with kde-plasma-destop
> 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. This appears indeed the the case debian stable (nouveau driver and kde wayland) Starting chromium without arguments hangs Starting chromium with --disable-gpu works Starting chromium with --ozone-platform=x11 works Probably same issue as reported on upstream: https://issues.chromium.org/issues/445738043 Frustrating as no idea where issue lies - chromium, kwin, mesa, kernel, ?? Best regards, Riku
Bug#1121656: Chromium freezes on Stable with kde-plasma-destop
Package: chromium Version: 142.0.7444.175-1~deb13u1 Chromium (but also Google Chrome) freezes if I install only kde-plasma-destop. I receive the following message: === samiel@debian:/opt/google/chrome$ google-chrome Created TensorFlow Lite XNNPACK delegate for CPU. [7405:7432:1129/215808.430422:ERROR:google_apis/gcm/engine/registration_request.cc:292] Registration response error message: DEPRECATED_ENDPOINT [7405:7432:1129/215831.147542:ERROR:google_apis/gcm/engine/registration_request.cc:292] Registration response error message: DEPRECATED_ENDPOINT [7405:7489:1129/215836.017232:ERROR:content/browser/browser_main_loop.cc:288] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed ... === Since this is a "minimal" installation, I believe it's not strictly a Chromium bug, but rather an overlooked dependency that isn't automatically installed. It would be important to identify this dependency and, if necessary, ensure the installation process ensures the presence of this additional essential package.
