Well some good news, that bug appears to have been squashed, certainly for myself and another user in the topic link that I gave.
It has I believe been resolved by a micro update, reboot your system and see if it is applied.
