Not sure why this has fixed itself, but the corresponding bug boo#1159620 is also fixed meanwhile. So no need to reopen it at that point.