Comment # 6 on bug 1158318 from
No, it still fails with version 0.5.1.


You are receiving this mail because: