@Tony: Can you reproduce this once again and record the HCI packets by running
$ sudo btmon -w test.cap Then attach test.cap here. -- 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/1551858 Title: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: Connecting to the latest generation Apple BT keyboard ( the one with the USB port & no batteries ) fails on an Ubuntu Touch device, as when you press the "Connect" button on the device page, a dialog titled "Bluetooth Pairing Request" is displayed, with the following text: Please confirm that the PIN displayed on 'Magic Keyboard' matches this one: XXXXXX The dialog has "Cancel" and "Confirm PIN" buttons. The keyboard has no display on which a PIN could be displayed. When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X, ... ) to connect this keyboard all that's necessary is to click/press the 'Connect' button in the appropriate place, and the keyboard automatically connects, and is usable with no other actions required from the user. Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez 5.36-0ubuntu2~overlay1 installed. Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37 installed from silo 39. Note, after dismissing the dialog, subsequent attempts to connect may not re-display the PIN dialog, instead nothing happens. I've found that this requires power cycling the keyboard to clear and cause the PIN dialog to be displayed again. [bluetooth]# show Controller B8:64:91:48:2B:1E Name: Aquaris E4.5 Ubuntu Edition Alias: Aquaris E4.5 Ubuntu Edition Class: 0x1c020c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0525 Discovering: no [bluetooth]# devices Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3 Device DE:76:E2:04:9D:6F BB-9D6F Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03 Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8 Device 84:38:35:67:0C:3D ubuntu-0 Device 04:69:F8:C2:A0:09 tony espy’s Keyboard Device 00:21:3C:A0:14:A6 Jawbone ERA Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7 Device info *before* pairing attempt: Device 04:69:F8:C2:A0:09 Name: tony espy’s Keyboard Alias: tony espy’s Keyboard Class: 0x002540 Icon: input-keyboard Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no Modalias: bluetooth:v004Cp0267d0066 No changes in any of the attributes after *after* the pairing attempt ( output of info command is the same ). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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
