> I've confirmed that this problem is still not fixed in the code of the > recently updated 3.0.24-2, but I was not able to reproduce it yet. Given the changelog of 3.0.24, there is indeed no reason at all for this bu to be fixed in it.