kernel-packages team mailing list archive

[Brian Burch <1490349@xxxxxxxxxxxxxxxxxx>]

Following a suggestion from jbmacbrodie to minimise the blueman device
manager after pairing, I tried again. This time, I used the command-line
bluetoothctl program as sudo: the "paired-devices" command showed the
device was already paired from my previous session. "info [mac addr]"
showed it was not legacy-paired and not currently connected.

I flicked the switch on the docking unit (a bluetooth keyboard with
touchpad) so it would try to establish a connection. I then issued the
"connect [mac addr]", and bluetoothctl briefly showed it was connected
and the blue LED on the keyboard changed from blinking, to solid on,
then back to solid off in a matter of a few seconds.

syslog showed:

Apr  8 15:28:39 Muscat bluetoothd[610]: Can't get HIDP connection info
Apr  8 15:28:40 Muscat kernel: [ 1066.735075] hid-generic 0005:0B05:8502.0004: unknown main item tag 0x0
Apr  8 15:28:40 Muscat kernel: [ 1066.735354] input: ASUS T300CHI DOCKING as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0004/input/input16
Apr  8 15:28:40 Muscat kernel: [ 1066.735950] hid-generic 0005:0B05:8502.0004: input,hidraw3: BLUETOOTH HID v0.01 Keyboard [ASUS T300CHI DOCKING] on 60:57:18:59:0a:64
Apr  8 15:28:40 Muscat bluetoothd[610]: No agent available for request type 0
Apr  8 15:28:40 Muscat bluetoothd[610]: device_request_pin: Operation not permitted

I had just rebooted the latest (4.4.0-17-generic) kernel and bluetoothd
logged the "not enough handles" message again when starting. I don't
know whether this is a symptom of the kernel bug, or something
completely different!

-- 
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: bluetoothd reports "Not enough 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