FYI, I just had this bug happen to me again with 4.2.1-3.

Reply via email to