Comment 83 for bug 1189850

That's unexpected - those updates should have had no impact upon this issue. :|