We have been unable to reproduce this bug under testing in 3.2 and 3.3 (with the caveat that it is a hard one to test) - have any of the earlier reporters of this bug had it occur in 3.2 or later?
We have been unable to reproduce this bug under testing in 3.2 and 3.3 (with the caveat that it is a hard one to test) - have any of the earlier reporters of this bug had it occur in 3.2 or later?