Are you sure you're on 2.0.5? I have seen this bug in 2.0.4 and this was the main reason for 2.0.5 - this newer version fixed this bug