Hello!

I just noticed this bug can't be reproduced anymore since linux 5.10.0-23-amd64 (5.10.179-1).   Hopefully this will help to track what was the exact issue and how did it got fixed.


Thanks!.

Reply via email to