Oops... that's not cool. But I did read somewhere about a fix for that, which arised when people had this problem with the leaked 1.2 firmware. At least it's fixable, but yeah...