summaryrefslogtreecommitdiff
path: root/src/adv_monitor.c
diff options
context:
space:
mode:
authorManish Mandlik <mmandlik@google.com>2020-12-02 19:46:51 -0800
committerLuiz Augusto von Dentz <luiz.von.dentz@intel.com>2020-12-02 21:08:38 -0800
commitdde267ea50f7c191a6fbb23e53acedc1f6722991 (patch)
tree4250ddc4f280bf15f49a10284d492aed71521429 /src/adv_monitor.c
parenta37d53db9ae7d21a8f812925303d767d3f03e597 (diff)
downloadbluez-dde267ea50f7c191a6fbb23e53acedc1f6722991.tar.gz
adv_monitor: Register client app with app-root-path
When a client app is registered with g_dbus_client_new(), bluez root path, i.e. "/", is used as the app root path and signal watches are added at that root path. Because of this, InterfacesAdded/InterfacesRemoved signals emitted by app - while creating/removing advertisement monitor objects at the app root path - are not received by bluetoothd. Use g_dbus_client_new_full() to register a client app with the correct app root path.
Diffstat (limited to 'src/adv_monitor.c')
-rw-r--r--src/adv_monitor.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/adv_monitor.c b/src/adv_monitor.c
index fc058dbf1..a5bc61c48 100644
--- a/src/adv_monitor.c
+++ b/src/adv_monitor.c
@@ -775,7 +775,7 @@ static struct adv_monitor_app *app_create(DBusConnection *conn,
app->manager = manager;
app->reg = NULL;
- app->client = g_dbus_client_new(conn, sender, path);
+ app->client = g_dbus_client_new_full(conn, sender, path, path);
if (!app->client) {
app_destroy(app);
return NULL;