Comment # 2 on bug 1176963 from
@Takashi: same issue unfortunately.


You are receiving this mail because: