It seems this issue (or at least a similar looking one has appeared again) Here is a report from one of my users
