The problem definitely still exists in 6.2.1 and should be fixed in 6.3.0. See this thread for more information.