Comment # 1 on bug 1003380 from
The problem seems to be solved after update to 2.16.3-1.11


You are receiving this mail because: