Audit which KDED services make sense to be user-disable-able
Some KDED services are user disable-able, and some are not.
A lot of the ones that are IMO don't really make sense to disable, especially ones that come from a package you can simply uninstall if you don't want to use that functionality, and where the provided functionality is critical such that major parts of the system stop working when they're disabled. Examples would be kscreen, kde-gtk-config, and bluedevil.
Others make no sense to be disable-able at all, such as the appmenu and vaults modules.These one should be auto-loaded when in use, and never loaded otherwise.
Others probably don't even need to be a KDED service, like the thing to handle Ctrl+Esc to launch the mini ksysguard. This can just be a global shortcut.
I bring this up because we've had bug reports that were caused by users disabling KDED modules to work around bugs and forgetting to turn them back on, or just doing it because they didn't understand what they were doing and then something broke.
We should audit with KDED modules actually make sense for the user to be able to disable.