Comment 19 for bug 1705345

I have the same problem, encountered at the first update after fresh 17.10 installation.