Andrew Parker wrote: > I saw this on 4.4.1 updating a single package (google-chrome-beta) so > its not a KDE update that causes this (at least in my case its not). This may be a completely different issue which just happens to cause the same symptoms. I don't use (nor even have installed) Chrome nor Chromium. Kevin Kofler