I'm would imagine that someone would have reported this problem in the past 8 months since 5.3 was released.