Yep, we'll be fixing this soon. Sorry for the trouble.
Edit: As of version 2.54, this issue has been fixed.
