kernel-packages team mailing list archive
Mailing list archive
[Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Tested with x230 and kernel 4.7-rc2 and finally managed to pair &
connect & use the MS Designer keyboard. I had to, however, jump over
fancy hops to accomplish that using u-s-s as there were glitches every
now and then [like multiple devices found even though there is only one
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
[Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Status in Unity Control Center:
Status in bluez package in Ubuntu:
Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly.
Bluetooth smart keyboard is unable to use after bluetooth-wizard says
"OK". Also the passcode input is also not acting interactively like
when pairing with bluetooth 3.0(LegacyPairing) keyboard.
Above scenario also being verified with bluetoothctl and blueman.
Step to reproduce:
1. open Bluetooth Settings
2. click on Add New Device button
3. select the bluetooth le keyboard
4. input the passcode display on GUI
After bluetooth-wizard telling user is okay the keyboard should work
Pairing mode stop on keyboard, but still not work.
More details about versions:
xenial daily (20160307)
bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1)
Designer Mouse, bluetooth smart (pairable, work, re-pair work)
Designer Keyboard, bluetooth smart (paired, not working)
BT3.0 keyboard, bluetooth classic (pair and work)
BT3.0 mouse, bluetooth classic (pair and work)
In control environment with the same hardware system and devices:
trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel)
bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5)
It works with all above devices but can only be pairing through
bluetoothctl manually, since the older bluetooth-wizard does not
understand bluez 5.x.
Everything seems works fine, although there are a lot more error
messages, but since this bug is more about xenial, please let me know
if we need more information about this, I'm able to reproduce this
trusty scenario in anytime.
A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box.
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
Date: Tue Mar 15 11:40:12 2016
InstallationDate: Installed on 2016-03-14 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude E5550
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Dell Inc.
dmi.board.vendor: Dell Inc.
dmi.chassis.vendor: Dell Inc.
dmi.product.name: Latitude E5550
dmi.sys.vendor: Dell Inc.
hci0: Type: BR/EDR Bus: USB
BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5
UP RUNNING PSCAN ISCAN
RX bytes:862538 acl:39687 sco:0 events:2668 errors:0
TX bytes:26235 acl:904 sco:0 commands:1021 errors:0
To manage notifications about this bug go to: