Comment 21 for bug 389686

I'm not sure what did it, but as of some updates today or late last night I'm also affected. Something's changed to trigger this behaviour, because it's the first I've seen of it in this development cycle.