[Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
1490349 at bugs.launchpad.net
Sat Jul 29 15:38:40 UTC 2017
Apr 27 '15
"I dived into the code for debugging the issue a little bit. The attrib_db_find_avail(adapter, svc_uuid, size)[in function: gatt_service_add()] always return 0. the root cause is the servers glist parameter is always NULL, which is in g_slist_find_custom(servers, adapter, adapter_cmp)[called from find_uuid16_avail()/find_uuid128_avail()].
I noticed there is the call: **btd_adapter_gatt_server_start**(struct btd_adapter *adapter)to be used to add a server into the servers glist. But the weird thing is no where it gets called through the whole bluez source code tree.
So shall I call btd_adapter_gatt_server_start() somewhere in my code? or any other steps I should do to resolve the issue?
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in Ubuntu.
15:10 and 16.04: bluetoothd "Failed to start discovery:
org.bluez.Error.NotReady" after bluetoothd restarted
To manage notifications about this bug go to:
More information about the Ubuntu-bluetooth