On March 24, 2017 8:32:35 AM PDT, Marc Chamberlin <marc@marcchamberlin.com> wrote:
On 03/23/2017 10:15 AM, Michael Hirmke wrote:
- kquitapp5 does not always work. Sometimes you have to kill plasmashell. - You could create a shortcut with some key combination.
This is my script for restarting plasmashell, because it hangs quite often here:
That doesn't work when it locks. I get the error:
$ "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : 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
On 03/24/2017 06:32 AM, James Knott wrote: the
network connection was broken."
Like Patrick's suggestion, it will restart plasmashell when everything is normal, but not when the problem occurs. The only way I can get out of it is to use Ctl-Alt-Backspace to force a desktop shutdown.
Sorry to be joining this thread late, but been on vacation... James, I too have been plagued by this failure on my laptop but for some mysterious reason, not on my desktop systems. They are all running the same version of OpenSuSE Leap42.2 and KDE/Plasma. I and others have also reported it, not only here on OpenSuSE but in other distros as well. Yes, the kicker bar freezes and nothing but open windows respond to the mouse or keyboard input. Something about Plasmashell appears to be sick...
The best solution I have found so far is to leave a Konsole shell window open on my desktop. That way I can also get to it so as to issue the following two commands -
killall plasmashell plasmashell &
Do not issue this as root, but just do it under your own user account. Basically kill the plasmashell and restart it without regard to process
ids. There are other ways to do this, as already has been pointed out, but like you I found problems and errors when I tried other approaches.
This seems to be the more reliable way for me to get my desktop/plasmashell back.
HTHs.... Marc...
This same problem plagued Manjaro months ago, and was resolved by regular kde updates. While it lasted I used Marc's solution keyed into the little command window that popped up after pressing alt-f2. Any need to do this disappeared months ago as Manjaro is a rolling release and regular kde upgrades came along and the problem went away. I believe it was traced to invisible remnants of a screen overlay that had crashed but was not completely shut down and was still intercepting mouse and keyboard inputs on some areas of the screen. There were numerous hits in bugs.kde.org on this issue. For me it occurred on Intel video chipset desktop fwif. I do not see this problem on leap 42.2. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org