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.
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:
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.
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
> 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
"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.
"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:
Further update: On Testing (Forky) — with Cinnamon and therefore X11 — I installed the Nvidia drivers, specifically, the old nvidia-tesla-470-driver package (from Sid, via pinning) because my Geoforce 760 is old (it still relies on the Kepler architecture). Google Chrome freezes again, and not infrequently. I deduce that Wayland isn't responsible, and neither are the Nouveau drivers...
Thanks for testing. FYI I just released chromium 143 for stable and oldstable, so that's another thing you can try.
Just installed. Stable - kde-plasma-desktop - wayland - nouveau Chromiun freezes at first start: https://ibb.co/k2nftYdp The two option work until now Il 04/12/25 22:44, Andres Salomon ha scritto:
Hi! i had this problem too! then i noticed that in my kde plasma about section plasma didnt actually recognize my rtx 2070 gpu! so i looked up a guide for updating my drivers and updated the nvidia open drivers and then rebooted and the problem went away! so i think its some kind of a driver problem!