I updated from 1.3.9 to 1.5.0 and have the same issue. I think post #21 solved it for me as well. It's too early to tell though.