[RFC 2/2] device: Fix the wrong order of UUIDs PropertyChanged

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The code goes to great length to make sure that the Service Discovery
is finished before sending the NewConnection() message to external
profiles.  In some situations this effort is wasted because the UUIDs
signal is emitted after NewConnection() is sent.

This patch fixes it by making sure that all the properties for that
object are updated before sending the NewConnection() call.
---
 src/device.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/device.c b/src/device.c
index ee17514..9f9dba3 100644
--- a/src/device.c
+++ b/src/device.c
@@ -2806,6 +2806,8 @@ static void search_cb(sdp_list_t *recs, int err, gpointer user_data)
 send_reply:
 	device_svc_resolved(device, err);
 
+	g_dbus_flush_properties(dbus_conn, req->device->path);
+
 	if (!device->temporary)
 		store_device_info(device);
 
-- 
1.8.2.1

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux