Comment # 2 on bug 1203805 from
First tests indicate that the issue is indeed gone.

Were there specific changes in that version which could explain this?


You are receiving this mail because: