[Bug 2084337] Re: Bluetooth headphones won't stay paired after upgrade to 24.10

See also bug 2081384.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084337

Title:
Bluetooth headphones won't stay paired after upgrade to 24.10

Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed

Bug description:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
been using with Ubuntu for several years now. Since I upgraded to
Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
I pair it again, every time.

This is how things worked with 24.04 LTS:

- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the headset autoconnects to my laptop and plays a little "I'm connected trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped things up by running a shell script to `bluetoothctl connect $headset_mac_address`)
- I can now play sounds through the headset

This is how thigs go with 24.10:

- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the second connection never comes through
- I run `bluetoothctl connect $headset_mac_address` and I get

Attempting to connect to 60:AB:D2:43:49:4D
[CHG] Device 60:AB:D2:43:49:4D Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown

- I open the Bose Connect app on my phone to look at the list of connections. It shows my phone and nothing else. It should be showing my laptop ("blynas") under History, and it used to do that before the upgrade.
- I click "Connect new..." in the phone app (or pull and hold the button on the headset itself to put it in pairing mode), I hear a "ready to be paired" trill, I run `bluetooth connect $headset_mac_address` again (or click connect in gnome-control-center), and it connects fine. I can play music and everything. "blynas" is shown in the Current list of connected devices

- I turn off the headset, I turn it back on
- the headset autoconnects to both the phone and the laptop, because I'm intentionally trying to reproduce the bug, so of course it won't bug.

Previously, whenever I turned the headset on after turning it off for
a longer span of time, I had to do the 'Connect new...' thing.

BTW once I tried to tell gnome-control-center to forget the headset,
then paired it fresh, which got me a fresh new LinkKey in
/var/lib/bluetooth/, and things worked fine until another turn-off-
wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
the-pairing-dance-again-please.

(I keep track of the link key changes because I have a Windows 10
partition on this machine and I sometimes boot it, so I need to keep
the link key synchronized between Ubuntu and the Windows registry,
otherwise the headset will work only in one of the two OSes. However
I haven't booted Windows in months if not years, so this should not be
relevant.)

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: bluez 5.77-0ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 12 15:24:54 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1949 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
dmi.bios.date: 07/25/2023
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JETA2W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN2JETA2W(1.80):bd07/25/2023:br1.80:efr1.15:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q0_BU_Think_FM_ThinkPadX390:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 38:00:25:8D:A7:83 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:90167 acl:152 sco:0 events:6236 errors:0
TX bytes:2703900 acl:2480 sco:0 commands:3016 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337/+subscriptions