"True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

[Curtis Mumby]

I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost the ability to connect to any kind of Bluetooth "True Wireless" earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth headphones connect correctly but all "True Wireless" style headphones briefly connect then disconnect immediately.

bluetoothctl output:

```
[bluetooth]# devices
Device C0:28:8D:1D:42:90 Jaybird X3
Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9)
Device 40:26:19:DC:12:E6 Apple AirPods

[bluetooth]# connect C0:28:8D:1D:42:90
Attempting to connect to C0:28:8D:1D:42:90
[CHG] Device C0:28:8D:1D:42:90 Connected: yes
Connection successful

[Jaybird X3]# connect 7C:38:AD:4A:C8:F9
ttempting to connect to 7C:38:AD:4A:C8:F9
[CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes
Failed to connect: org.bluez.Error.Failed

Jaybird X3]# connect 40:26:19:DC:12:E6
Attempting to connect to 40:26:19:DC:12:E6
[CHG] Device 40:26:19:DC:12:E6 Connected: yes
Failed to connect: org.bluez.Error.Failed

[CHG] Device 40:26:19:DC:12:E6 Connected: no
[CHG] Device 40:26:19:DC:12:E6 Connected: yes
[CHG] Device 40:26:19:DC:12:E6 Connected: no

[Jaybird X3]#

```

```
$ lsb_release -rd

Description: Ubuntu 20.04 LTS
Release: 20.04
```

possible packages involved:
-pulseaudio
-pulseaudio-module-bluetooth
-bluez

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: curtis 8167 F.... pulseaudio
 /dev/snd/controlC2: curtis 8167 F.... pulseaudio
 /dev/snd/pcmC2D0c: curtis 8167 F...m pulseaudio
 /dev/snd/controlC0: curtis 8167 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 10 15:52:42 2020
InstallationDate: Installed on 2019-05-24 (352 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago)
dmi.bios.date: 06/20/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1204
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-AR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you add your 'journalctl -b 0' log after getting the issue?

Reassigning to linux rather than alsa-driver since that's more a bluetooth level issue than a sound one

[Curtis Mumby (jornadapro)]

Here is the output from `journalctl -b 0`:

$ journalctl -b 0
-- Logs begin at Sun 2020-05-03 06:17:09 EDT, end at Fri 20>
May 14 12:11:14 user-linux kernel: microcode: microcode u>
May 14 12:11:14 user-linux kernel: Linux version 5.4.0-29>
May 14 12:11:14 user-linux kernel: Command line: BOOT_IMA>
May 14 12:11:14 user-linux kernel: KERNEL supported cpus:
May 14 12:11:14 user-linux kernel: Intel GenuineIntel
May 14 12:11:14 user-linux kernel: AMD AuthenticAMD
May 14 12:11:14 user-linux kernel: Hygon HygonGenuine
May 14 12:11:14 user-linux kernel: Centaur CentaurHauls
May 14 12:11:14 user-linux kernel: zhaoxin Shanghai
May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS>
May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS>
May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS

[You-Sheng Yang (vicamo)]

Please do:

  1. reboot
  2. run `sudo btmon -w btsnoop.log` in a separate terminal,
  3. pair/connect your device once,
  4. when the connection disconnects, interrupt the btmon log capture,
  5. run `journalctl -b > journal.log`,
  6. attach btsnoop.log and journal.log here as attachments

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]