Comment # 3 on bug 1191945 from
It's been some time since the update with the potential fix was released. Have
you seen this problem again or can I assume that the new handling fixed it?


You are receiving this mail because: