[Dell Precision 5510][Yakkety] Unable to scan bluetooth classic devices but only LE devices
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Using 16.04 daily image: 20160919(
With testing package for 4.8 kernel: ppa:canonical-
Chip: 0a5c:6410 Broadcom Corp
Unable to scan/found bluetooth devices.
Steps to reproduce:
1. open bluetooth setting
2. click + to add new device
3. 'Device Search' and put bluetooth device in pairing mode
Expected results:
Found the device in pairing mode
Actual result:
Unable to find this 'Microsoft Bluetooth Notebook 5000'
Additional note:
Even though it can scan LE devices but still failed to pair with LE device
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: bluetooth (not installed)
ProcVersionSign
Uname: Linux 4.8.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 21 14:13:23 2016
InstallationDate: Installed on 2016-09-19 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160918)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
Bus 001 Device 003: ID 0c45:6713 Microdia
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5510
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/30/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: C4:8E:8F:E2:32:9A ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:2100 acl:0 sco:0 events:157 errors:0
TX bytes:4032 acl:0 sco:0 commands:132 errors:0
The above system information is from a 16.10 machine (which is end-of-life), but you report that the problem exists in 16.04.
Please log a new bug with details from the 16.04 machine affected.