Comment # 6 on bug 70053 from 
No this patch (v2) does not solve the problem.

You are receiving this mail because: