Bluetooth headphones and microphone not detected

Bug #1911441 reported by Dvbnhbq
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
New
Undecided
Unassigned

Bug Description

Trouble when connecting paired bluetooth headphones on Ubuntu 20.04.
The bluetooth headphones can be paired, but not connected.

```
$ bluetoothctl

# scan on
Discovery started
[CHG] Controller F0:85:C1:FF:BD:A8 Discovering: yes
[NEW] Device FC:58:FA:CF:D0:01 BT-1100
# scan off
Discovery stopped
[CHG] Controller F0:85:C1:FF:BD:A8 Discovering: no
[CHG] Device FC:58:FA:CF:D0:01 RSSI is nil
# devices
Device FC:58:FA:CF:D0:01 BT-1100
# pair FC:58:FA:CF:D0:01
Attempting to pair with FC:58:FA:CF:D0:01
[CHG] Device FC:58:FA:CF:D0:01 Connected: yes
[CHG] Device FC:58:FA:CF:D0:01 Connected: no
[CHG] Device FC:58:FA:CF:D0:01 Connected: yes
[CHG] Device FC:58:FA:CF:D0:01 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:CF:D0:01 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:CF:D0:01 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:CF:D0:01 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:CF:D0:01 ServicesResolved: yes
[CHG] Device FC:58:FA:CF:D0:01 Paired: yes
Pairing successful
[CHG] Device FC:58:FA:CF:D0:01 ServicesResolved: no
[CHG] Device FC:58:FA:CF:D0:01 Connected: no
# connect FC:58:FA:CF:D0:01
Attempting to connect to FC:58:FA:CF:D0:01
[CHG] Device FC:58:FA:CF:D0:01 Connected: yes
[CHG] Device FC:58:FA:CF:D0:01 Connected: no
Failed to connect: org.bluez.Error.Failed
[CHG] Device FC:58:FA:CF:D0:01 Connected: yes
[CHG] Device FC:58:FA:CF:D0:01 Connected: no
```

Logs:
```
Jan 05 00:59:00 host1 bluetoothd[536]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Jan 05 00:59:02 host1 bluetoothd[536]: connect error: Connection reset by peer (104)
Jan 05 00:59:37 host1 bluetoothd[536]: connect error: Connection reset by peer (104)
```

Pulseaudio configs:
```
$ grep -P '(bluetooth|bluez)' /etc/pulse/default.pa /etc/pulse/system.pa
/etc/pulse/default.pa:#.ifexists module-bluetooth-policy.so
/etc/pulse/default.pa:load-module module-bluetooth-policy
/etc/pulse/default.pa:#.ifexists module-bluetooth-discover.so
/etc/pulse/default.pa:load-module module-bluetooth-discover
/etc/pulse/system.pa:load-module module-bluez5-device
/etc/pulse/system.pa:load-module module-bluez5-discover
```

Packages installed:
```
$ dpkg -l | grep -P '(bluetooth|bluez)'
ii blueman 2.1.2-1ubuntu0.2 amd64 Graphical bluetooth manager
ii bluez 5.53-0ubuntu3 amd64 Bluetooth tools and daemons
ii bluez-obexd 5.53-0ubuntu3 amd64 bluez obex daemon
ii bluez-tools 2.0~20170911.0.7cb788c-2build1 amd64 Set of tools to manage Bluetooth devices for linux
ii libbluetooth3:amd64 5.53-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack
ii pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.8 amd64 Bluetooth module for PulseAudio sound server
```

```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

$ uname -a
Linux host1 5.4.0-59-generic #65-Ubuntu SMP Thu Dec 10 12:01:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
```

Please help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
Uname: Linux 5.4.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CasperMD5CheckResult: skip
Date: Wed Jan 13 17:18:39 2021
PackageArchitecture: all
ProcEnviron:
 TERM=st-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8.17
dmi.board.asset.tag: Default string
dmi.board.name: CITI E202 ES2002EW
dmi.board.vendor: Digma
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 31
dmi.chassis.vendor: Digma
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/14/2018:svnDigma:pnCITIE202ES2002EW:pvrDefaultstring:rvnDigma:rnCITIE202ES2002EW:rvr1.0:cvnDigma:ct31:cvrDefaultstring:
dmi.product.family: EMI30P3S6M22L18B320T4C00W1H2G0G3A1C2P1C0D0C1801M0N1X1WOS
dmi.product.name: CITI E202 ES2002EW
dmi.product.sku: 20180313288
dmi.product.version: Default string
dmi.sys.vendor: Digma

Revision history for this message
Dvbnhbq (dvbnhbq) wrote :
affects: ubuntu → alsa-driver (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.