https://bugs.kde.org/show_bug.cgi?id=288881
--- Comment #3 from Daniele E. Domenichelli <daniele domenichelli gmail com> 2011-12-13 14:52:37 --- This might be a little hacky but it should work: To ensure the correct loading order the approver we could have a file in /usr/share/dbus-1/services/org.freedesktop.Telepathy.Client.KDE.Approver.service [D-BUS Service] Name=/usr/share/dbus-1/services/org.freedesktop.Telepathy.Client.KDE.Approver Exec=qdbus org.kde.kded /kded org.kde.kded.loadModule telepathy_kde_approver and no client file. Instead of starting the approver automatically at login, when MC starts, it will see that dbus is able to start a client that didn't install any .client file, therefore will start it to check its capabilities (this is what haze does, because it cannot have a .client file since its capabilities depend on the plugins installed). Then usually telepathy stuff (haze, for example) will exit and will be activated later on demand, but the kded module won't be unloaded and we will have the approver always running. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
