> This seems to be another case of mixed framework package versions, > 5.22 en > 5.23. > > Can you try whether the fix described in > https://lists.debian.org/debian-kde/2016/07/msg00065.html fixes your > issue too?
That was indeed the case. Upgrading all listed packages to 5.23 from sid fixed it for me. Why is there no protection against this sort of thing? It's been broken for more than a week now...
