Everytime I switch to an external monitor and launch skype using the launcher in the icon-only task manager, plasma-desktop becomes unresponsive and I need to kill it and launch it again. It comes back almost fine (some layout glitches). Interestingly, skype is launched and works fine independently of the panel. I can understand that skype is closed-source, so it is probably doing something wrong. On the other hand, random programs should not able to easily hang plasma-desktop. Reproducible: Always
The culprit is X-DBUS-StartupType=unique more info at: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1082394
I'm facing a similar problem, that seem to be related to "X-DBUS-StartupType=unique" Reproducible: Always Tested KDE Version: 5.8.4 / 5.8.6 Impact: Critical Description: Place a .desktop file on your workspace. Set "launch as seperate user" and select an existing login (blafoo for example). Set "DBUS Registration" to unique (default on most desktop files). The resulting .desktop file will contain: X-DBUS-StartupType=unique X-KDE-SubstituteUID=true X-KDE-Username=blafoo Launch the .desktop file. Kdesu will show up and let you enter blafoo's password. At this point the plasmashell is already froozen and keeps waiting until the spawned process is killed (either kdesu or the launched application if you already entered the user's password). The plasmashell doesn't freeze with X-DBUS-StartupType=unique, X-KDE-SubstituteUID=false and it doesn't freeze with X-DBUS-StartupType=wait, X-KDE-SubstituteUID=true.
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