The fix for this could be the same for the auth handler: do not autostart it, but install a client file and let mission control start it (see https://bugs.kde.org/show_bug.cgi?id=288881)
Related (if not duplicate): https://bugs.kde.org/show_bug.cgi?id=284779
I'm not sure we can make all of KDED started by MC, that would cause issues for eveyrone else :-) If we went with that we'd have to split it out into a separate app, which isn't impossible but I don't know if it's a good idea.
Not the whole kded, just the kcm-kded-module :P Or perhaps I didn't get the comment...
Git commit 908acec6de7e037f2f8aac41b04126fc7061a77a by Daniele E. Domenichelli. Committed on 06/03/2012 at 13:54. Pushed by ddomenichelli into branch 'master'. Do not load module automatically but by MC when it is started See ktp-approver commit 5ebe32c9cce383fb998356adc07adb90baa18d8a Reviewed-by: Martin Klapetek <martin.klapetek@gmail.com> Related: bug 284779 M +5 -0 CMakeLists.txt M +2 -3 kded_ktp_integration_module.desktop A +3 -0 org.freedesktop.Telepathy.Client.KTp.KdedIntegrationModule.service.in http://commits.kde.org/telepathy-kded-module/908acec6de7e037f2f8aac41b04126fc7061a77a