Comment # 2 on bug 1138954 from
I confirm that this change fixes this issue.


You are receiving this mail because: