None of the KDED modules provide a X-KDE-DBus-ServiceName, so there are
a lot of warnings during session startup.
Not providing the entry actually is no error, as:
- modules are loaded and requested using the org.kde.kded5 service
- org.kde.kded5 already is a singleton, so protecting against multiple
instances of the module is not necessary.