I saw the same behaviour on an s3virge system with 6.8.2-5; is it likely to be fixed as well, or a different bug?
I saw the same behaviour on an s3virge system with 6.8.2-5; is it likely to be
fixed as well, or a different bug?