today's release of linux-image-5.10.0-4-amd64 / linux/5.10.19-1 has fixed this bug for me. I suggest to close this bug report now.

Thanks again!

Reply via email to