Sorry for the confusion (which actually seems to have started in comment
#1 :).
This bug is not about "Not enough free handles to register service".
This bug (as first reported by TJ) is about "Failed to start discovery:
org.bluez.Error.NotReady" which happens after restarting the daemon. And
actually, it seems that's not a bug. "scan on" fails because the
controller (your bluetooth hardware) is turned off by default. All you
need to do is type "power on" before "scan on".
If anyone would like to log a separate bug for "Not enough free handles
to register service" then please feel free :)
** Description changed:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
- $ sudo systemctl start bluetooth
- $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
- 23:31:53 systemd[1]: Starting Bluetooth service...
- 23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
- 23:31:53 systemd[1]: Started Bluetooth service.
- 23:31:53 bluetoothd[16647]: Starting SDP server
- 23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
- 23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
- 23:31:53 bluetoothd[16647]: Not enough free handles to register service
- 23:31:53 bluetoothd[16647]: Error adding Link Loss service
- 23:31:53 bluetoothd[16647]: Not enough free handles to register service
- 23:31:53 bluetoothd[16647]: Not enough free handles to register service
- 23:31:53 bluetoothd[16647]: Not enough free handles to register service
- 23:31:53 bluetoothd[16647]: Current Time Service could not be registered
- 23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
- 23:31:53 bluetoothd[16647]: Not enough free handles to register service
- 23:31:53 bluetoothd[16647]: Not enough free handles to register service
- 23:31:53 bluetoothd[16647]: Sap driver initialization failed.
- 23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
- 23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
- 23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
-
- And
+ $ sudo systemctl restart bluetoothd
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
** Summary changed:
- 15:10 and 16.04: bluetoothd reports "Not enough free handles to register
service" at start
+ 15:10 and 16.04: bluetoothd "Failed to start discovery:
org.bluez.Error.NotReady" after bluetoothd restarted
** Description changed:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
- $ sudo systemctl restart bluetoothd
+ $ sudo systemctl restart bluetooth
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
** Changed in: bluez (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10 and 16.04: bluetoothd "Failed to start discovery:
org.bluez.Error.NotReady" after bluetoothd restarted
Status in bluez package in Ubuntu:
Invalid
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl restart bluetooth
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
