Comment 13 for bug 1490349

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!