So the issue lies with dbus-cpp not starting a bus listener instance on the client if there is no explicit request from the client to be exposed on the bus. The client "connection" therefore cannot serve messages pushed to it.
I don't know if this follows the DBus specification to the letter so I will now proceed to add something to platform-api to manually start the bus listener while dbus-cpp itself gains the capabilities. However, perhaps we should check if it is indeed expected by the spec to have the client listen if it hasn't exported itself explicitly on the bus, otherwise Autopilot may be making an incorrect assumption.
Chris,
So the issue lies with dbus-cpp not starting a bus listener instance on the client if there is no explicit request from the client to be exposed on the bus. The client "connection" therefore cannot serve messages pushed to it.
I don't know if this follows the DBus specification to the letter so I will now proceed to add something to platform-api to manually start the bus listener while dbus-cpp itself gains the capabilities. However, perhaps we should check if it is indeed expected by the spec to have the client listen if it hasn't exported itself explicitly on the bus, otherwise Autopilot may be making an incorrect assumption.