STEPS TO REPRODUCE 1. Open systemd entry in systemsettings 2. Do any systemd action 3. Interact with the window (switching settings entry, trying to close the window) OBSERVED RESULT Window is greyscaled and kwin_killer_helper is started after systemd task has completed EXPECTED RESULT Add a visual feedback that something is happening when a systemd task/action is executed or running. As systemsettings isn't actually hanging an option to kill it should not be offered. If possible, the systemsettings window should remain responsive during the task. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 5.10.24-200.fc33.x86_64 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2
Sounds like it's blocking somewhere? Is that shipped by us?
(In reply to David Redondo from comment #1) > Sounds like it's blocking somewhere? Is that shipped by us? It seems that this might be part of Fedora, though I can't track it down exactly. Will file a bug at redhat.bugzilla.com though.
That's https://invent.kde.org/unmaintained/systemd-kcm Which appears to be unmaintained now, so I'll get the ball rolling to get that removed from fedora
I'll take the liberty of closing this, as unmaintained (and unsupported)
It looks like the replacement is https://invent.kde.org/system/systemdgenie which I am going to look into packaging. (But I don't know whether this missing feature is actually implemented there yet.)
And Rex, if you want kcm_systemd removed from Fedora sooner, then packaging SystemdGenie is the idea. :-) I object to removing the KCM before the standalone application is packaged as a replacement with proper Obsoletes in place.
I don't even if Systemd-Genie can be considered its replacement. It looks like it has had barely any non-localization commits in the past four years. :/
Well, it is according to the author: https://rthomsen6.wordpress.com/2016/12/18/introducing-systemdgenie/ but the codebase has always been only sporadically updated.