Since upgrading to KDE 4.14.2 in random intervals (from 5 minutes to hours) the process plasma-desktop takes up 100% CPU. Changing desktops or opening new programs is then not possible. However the already open applications are still usable. Currently I kill plasma-desktop and restart it by hand. This helps until the next lock up. The last output in the terminal where I restart plasma-desktop is always void DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." This gets repeated every minute or so until I kill the frozen process and restart it. Reproducible: Always Steps to Reproduce: 1. Login into KDE 4.14.2 2. Wait between 5 minutes to an hour 3. plasma-desktop takes up 100% CPU and freezes KDE is installed from the 4.14.2 packages for Ubuntu trusty from https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports?field.series_filter=trusty $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty
This is either caused by a faulty plasma widget, or by a faulty kded module. To find the offender, please try to remove specific widgets, or try to disable kded modules. For further information about debugging kded, please see http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/
Comment from GCI student: I use Ubuntu 14.10 with KDE 4.14.2 and everything works good!
I found the culprit. Every time I run the winswitch_applet from https://winswitch.org for approximately an hour the error message appears and plasma-desktop freezes. This also happens at KDE 4.14.2 The ticket for winswitch can be found at https://winswitch.org/trac/ticket/278#ticket Christian
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham