kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #167413
[Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
** Tags added: 201406-15271 taipie-lab
--
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/1557298
Title:
[Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Status in Unity Control Center:
New
Status in bluez package in Ubuntu:
New
Bug description:
Failed to pair low energy(bluetooth smart, 4.0 or 4.1) devices
correctly.
1. bluetooth smart mouse is being listed as "all type" in bluetooth-
wizard, however it is able to be paired and use, even repair(i'm
mentioning this because in some circumstance low energy device can be
only paired once, bug #1515179)
2. 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 keyboard.
Above scenario also being verified with bluetoothctl and blueman.
-
More details about versions:
Environment:
xenial daily (20160307)
bluez 5.37-0ubuntu5
gnome-bluetooth 3.18.2-1ubuntu2
blueman 2.0.3-1ubuntu1
bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1)
Tested devices:
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, 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.
-
Additional note:
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.
ProblemType: Bug
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
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
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
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0141B2
dmi.board.vendor: Dell Inc.
dmi.board.version: X02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5550
dmi.sys.vendor: Dell Inc.
hciconfig:
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:
https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions
References