That sounds like an excellent workaround. It's probably not a fix
though. A fix would involve finding out why the config has confused
bluez.

Actually this sounds like an "old" bug that was fixed after 16.04 since newer 
releases aren't being reported. If we could figure out what fixed it then we 
could backport that fix to 16.04. You can search the code here:
   https://git.kernel.org/pub/scm/bluetooth/bluez.git

-- 
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 reports "Not enough free handles to
  register service" at start

Status in bluez package in Ubuntu:
  Confirmed

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 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

  $ 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

Reply via email to