Comment # 2 on bug 1003286 from
Identical issue occurs in RC1 as well, FYI.


You are receiving this mail because: