On Wed, Jan 11, 2012 at 1:28 PM, Chris Kühl <[email protected]> wrote: > On Tue, Jan 10, 2012 at 8:31 AM, Patrick Ohly <[email protected]> wrote: >> On Mo, 2012-01-09 at 18:59 +0100, Chris Kühl wrote: >>> On Mon, Jan 9, 2012 at 4:54 PM, Patrick Ohly <[email protected]> wrote: >>> > commit bf293d0b10e60d3c269a41b4f2b51aea0c54943b >>> > Author: Patrick Ohly <[email protected]> >>> > Date: Mon Jan 9 14:38:49 2012 +0100 >>> > >>> > fork/exec: implemented stop() and kill() >>> > >>> > Sending the signals was missing. >>> > > > I've run into an issue when trying to use signals between the child > and parent. When activating the signal it tries to use > dbus_bus_add_match which tries in turn to call AddMatch on the > org.fredesktop.DBus interface which is not available. I've modified > the dbus-client-connection.cpp example to expose this[1] and am > looking into fixing it. > > I'm thinking this will not be an issue with the GIO GDBus wrapper.
This will very much be an issue with GIO GDBus as it uses the same mechanism. Looking that the souce of libdbus and gdbus leads me to believe using signals on a non-bus connection doesn't really make sense. I just use method calls in this case. Cheers, Chris > > [1] > https://meego.gitorious.org/meego-middleware/syncevolution/commit/2b39a0410d5b8f362e3453ede17f980f494e0c10 > > Cheers, > Chris _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
