I did a fresh install of 5.0 yesterday and I have not (yet) encountered that problem.

Reply via email to