I fixed that in 2.0.2. And now it's back.
Fixed without revision bump.
*** Bug 596974 has been marked as a duplicate of this bug. ***