I guess that’s the same problem as @Segertas mentioned in an other forum post:
The same bug was also mentioned a few months back, at the end of January: