Though it is listed in OS 1.02B as fixed, the bug is still present for me in OS 1.02C.
Can anyone confirm?