Following is a comment from Nik Lutz (veromix maintainer): ---------------------- I think I experienced the same problem (in ubuntu) multiple times during updates to newer kde versions. The bug you are referring to is from 2012 and I'am sure python plasmoids worked shortly after that (else there would be more reports).
According to http://packages.qa.debian.org/k/kde-workspace.html there where several new package-uploads to debian testing during the last month I belive that they where built/linked against an older python version, or python-scriptengine-python was built/linked against an older version of kde. Most probably this problem gets solved during the next weeks - in the meantime you could try to build kde-workspace yourself (in case you have enough time and diskspace: apt-get source kde-workspace ; apt-get build-dep kde-workspace; cd kde-workspace ; dpkg-buildpackage -b) ------------------------ -- Xavier -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6307206.QG6WebhYl7@gilgamesh
