Comment # 3 on bug 101360 from
The attached patch fixes the issue for me.


You are receiving this mail because: