Hi Aaron. Thanks for the quick reply. On Tue, Mar 23, 2010 at 5:53 PM, Aaron J. Seigo <ase...@kde.org> wrote: > my guess would be that the dbus service does not exist yet. the code probably > just needs to track the service coming and going. in fact, given your > description, i assume that it probably also breaks if you stop the service and > start it again while plasma-* is running. > > see kdebase/workspace/plasma/desktop/runners/plasma-desktop for a small and > simple example of how to watch for a dbus service being available.
Based on what I see, I don't think this is the case. The service is configured to automatically start up when a client tries to connect to it. I've set this up via configuration in "/usr/share/dbus-1/system-services" and it works fine, but only after I restart Plasma, not before. In fact, once the service is up and running, I can pkill it, and it starts right back up again if a data engine is using it, which is kinda cool. The only problem is that none of this works until I bounce Plasma. Even if I start up the service manually (i.e. not relying D-Bus auto-activation), I get an error when the data engine tries to connect. Not the same error, but an error nonetheless. I have tried sending SIGHUP to the dbus-daemon processes, but that doesn't help. The only way I've been able to make it work is by restarting Plasma. _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
