I have good news on that issue: in the most recent security update 100.0.4896.60-1~deb11u1 the issue is fixed for me. Chromium starts with my usual flags in /etc/environment
CHROMIUM_FLAGS="--enable-features=UseOzonePlatform --ozone-platform=wayland" So this is fixed for me. Thanks, Andreas
