> 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

Reply via email to