Created attachment 87744 [details] Screenshot The end process dialog / killer helper sometimes only shows a snapshot, so it would not let the user kill the process.
What do you see if you suspend the compositor (press "Shift+Alt+F12") in such case? The screenshot only shows ksysguard, does really happen the same thing for the "kill helper" (when you attempt to close a window and it doesn't react within 10 seconds, kwin will offer to kill it - that's the "actual" kill helper)
(In reply to Thomas Lübking from comment #1) > What do you see if you suspend the compositor (press "Shift+Alt+F12") in > such case? > > The screenshot only shows ksysguard, does really happen the same thing for > the "kill helper" (when you attempt to close a window and it doesn't react > within 10 seconds, kwin will offer to kill it - that's the "actual" kill > helper) Disabling the compositor does not change this behaviour. I thought the kill helper did the same (perhaps because of a screenshot the end process dialog made of it), but it works normal. I
Created attachment 87745 [details] Screenshot2
It seems the areas within the end process dialog and the system monitor get unmanaged, so overlaying them with other windows lets you draw on them, See Screenshot2.
This looks like making use of Qt::WA_NoSystemBackground and never painting anything. Re-assigning to ksysguard (Not in the compositor -> not in KWin) @jhnnslschnr, you could try whether this happens if you run: ksysguard --style windows
(In reply to Thomas Lübking from comment #5) > @jhnnslschnr, you could try whether this happens if you run: > > ksysguard --style windows The only difference is, that the content of the areas won't change if you overlay them with other windows, but ksysguard and it's dialog are still freezed.
Which version are you using? Could you please post the output of: ksysguard --version
(In reply to Arjun Ak from comment #7) > Which version are you using? Could you please post the output of: > > ksysguard --version $ ksysguard --version Qt: 5.3.1 KDE Development Platform: TODO System Monitor:
I have the same issue. ksysguard actually hangs when you try to kill a process, and the only wait to exit it is to kill ksysguard.
BTW, this only happens with the Plasma 5 version, it works fine under KDE4.
Fixed for me, probably by updating packages.
(In reply to AnAkkk from comment #11) > Fixed for me, probably by updating packages. What sources are you using? This bug is still present for me, i compiled on arch linux from AUR yesterday evening. The "screenshot" behaviour also happens in other KDE 5 apps when they hang, so the actual bug is that ksysguard hangs when trying to end a process.
(In reply to jhnnslschnr from comment #12) > (In reply to AnAkkk from comment #11) > > Fixed for me, probably by updating packages. > > What sources are you using? > This bug is still present for me, i compiled on arch linux from AUR > yesterday evening. > > The "screenshot" behaviour also happens in other KDE 5 apps when they hang, > so the actual bug is that ksysguard hangs when trying to end a process. The same AUR packages, except that I've changed them to install in /usr instead of /opt/kf5. I had all kinds of issues when it was installed in /opt/kf5, this might be another one of them.
I just tried the current project neon iso, where ksysguard works fine, too. So this seems to be an issue of the AUR package, not of ksysguard itself.