Hello Maintainers, Existing advertisement monitor implementation registers client app with bluez-root-path i.e. "/". Because of which client app needs to emit InterfacesAdded and InterfacesRemoved signals - when monitor objects are added or removed - at the bluez-root-path. This may cause confusion for application developers as the app need to register with bluez with app-root-path for exposing monitor object, but need to emit InterfacesAdded and InterfacesRemoved signals on the bluez-root-path. This patch series fixes advertisement monitor implementation to register client with client specified app-root-path. Also, adds support in gdbus library to emit signals at the app-root-path so that bluetoothctl can emit InterfacesAdded/InterfacesRemoved signals correctly when adv- monitors are created. These changes are verified by running the bluetoothctl as well as the python tester app and verifying that the monitor objects are getting exposed and DeviceFound/DeviceLost events are getting invoked correctly. Regards, Manish. Manish Mandlik (3): adv_monitor: Register client app with app-base-path gdbus: Emit InterfacesAdded/Removed at app root path client: Fix add advertisement monitor client/adv_monitor.c | 3 ++- gdbus/gdbus.h | 15 +++++++++++++++ gdbus/object.c | 39 ++++++++++++++++++++++++++++++--------- src/adv_monitor.c | 2 +- 4 files changed, 48 insertions(+), 11 deletions(-) -- 2.29.2.454.gaff20da3a2-goog
