Bluetooth devices can't reconnect after reboot or sleep

[Sitsofe Wheeler]

[ Impact ]

Bluetooth devices fail to reconnect after a suspend or system restart

[ Test Plan ]

1. Put the headphones into discovery mode.
2. Go to Settings -> Bluetooth and connect to the headphones.
3. Reboot the laptop.
4. Go to Settings -> Bluetooth
5. Click on the headphones.
6. Try to connect to the headphones.
7. If step 6. fails try to disconnect.
8. Go to step 6.

Expected result:
After step 6 for headphones to be connected and for headphones to announce "Bluetooth connected".

[ Where problems could occur ]

The change is in the reading of stored device keys. If the patch is wrong it could be that paired devices will not reconnect correctly or might use an incorrect profile.

[ Other Info ]

How reproducible is the problem:
Fairly reproducible. It can sometimes takes 30 or more connection attempts before a real connection is established.

Version information:
Ubuntu 24.10

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
Uname: Linux 6.11.0-9-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/seq: sitsofe 8130 F.... pipewire
 /dev/snd/controlC0: sitsofe 8136 F.... wireplumber
 /dev/snd/controlC1: sitsofe 8136 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 21 21:34:28 2024
InstallationDate: Installed on 2024-10-14 (7 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
MachineType: LENOVO 82KD
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 1.42
dmi.bios.vendor: LENOVO
dmi.bios.version: GLCN42WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo V15 G2 ALC
dmi.ec.firmware.release: 1.42
dmi.modalias: dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC:
dmi.product.family: V15 G2 ALC
dmi.product.name: 82KD
dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC
dmi.product.version: Lenovo V15 G2 ALC
dmi.sys.vendor: LENOVO

[Sitsofe Wheeler (sitsofe)]

Looks like this is actually related to bluez in some fashion. Here's what I'm seeing while running
journalctl -fu bluetooth
Nov 05 21:14:30 lenovo bluetoothd[374859]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:14:30 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:14:32 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:14:46 lenovo bluetoothd[374859]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:14:46 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:14:49 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:14:58 lenovo bluetoothd[374859]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:14:58 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:01 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:16 lenovo bluetoothd[374859]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:16 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:19 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:40 lenovo bluetoothd[374859]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:40 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:43 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:44 lenovo bluetoothd[374859]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:44 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:47 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:53 lenovo bluetoothd[374859]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:53 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:15:56 lenovo bluetoothd[374859]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 11:22:33:44:55:66: Connection refused (111)
Nov 05 21:...

[Sitsofe Wheeler (sitsofe)]

This might be related to bug #2084337 ...

[Sitsofe Wheeler (sitsofe)]

In fact bug #2081384 might be a better duplicate.

[Sitsofe Wheeler (sitsofe)]

Thanks to https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/comments/4 I've been able to manually rebuild the bluez debs with a patch of commit https://github.com/bluez/bluez/commit/366a8c522b648f47147de4852c5c030d69b916b3 and my headphone connection woes have been solved. I'll attach the patch here.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "bluez-fix-address.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mike Rans (rans)]

Thank you Sitsofe. That patch worked for me. For any who want to try it, I followed this guide to rebuild a Debian package: https://www.linuxjournal.com/content/rebuilding-and-modifying-debian-packages, then before the debuild step, applied the patch with patch -p1 < bluez-fix-address.patch.

[Sebastien Bacher (seb128)]

I've uploaded a SRU with the patch now

[Timo Aaltonen (tjaalton)]

Hello Sitsofe, or anyone else affected,

Accepted bluez into oracular-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.77-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-oracular to verification-done-oracular. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-oracular. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Arif Ali (arif-ali)]

I have tested the package, and had the same issue, and wouldn't reconnect before-hand.

My device can now connect with this patch

Below was my installation today

[11:26:31] [~] ❱❱❱ sudo apt install bluez/oracular-proposed
Selected version '5.77-0ubuntu2' (Ubuntu:24.10/oracular-proposed [amd64]) for 'bluez'
<snip>
Upgrading:
  bluez

Summary:
  Upgrading: 1, Installing: 0, Removing: 0, Not Upgrading: 1
  Download size: 1,412 kB
  Space needed: 20.5 kB / 10.9 GB available

Get:1 http://archive.ubuntu.com/ubuntu oracular-proposed/main amd64 bluez amd64 5.77-0ubuntu2 [1,412 kB]
Fetched 1,412 kB in 0s (6,433 kB/s)
(Reading database ... 326845 files and directories currently installed.)
Preparing to unpack .../bluez_5.77-0ubuntu2_amd64.deb ...
Unpacking bluez (5.77-0ubuntu2) over (5.77-0ubuntu1) ...
Setting up bluez (5.77-0ubuntu2) ...
Processing triggers for man-db (2.12.1-3) ...
Processing triggers for dbus (1.14.10-4ubuntu5) ...

[Andreas Hasenack (ahasenack)]

Like with other packages I have seen[1] in my shift, there are also tons of "in progress" autopkgtests for this package that don't seem to be running at all, yet are flagged as such in the report.

I'll trigger new runs for those:
$ ./retry-autopkgtest-regressions -s oracular --state RUNNING --blocks bluez
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=amd64&package=asterisk&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=arm64&package=asterisk&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=ppc64el&package=asterisk&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=s390x&package=asterisk&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=i386&package=bleak&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=amd64&package=bluez&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=s390x&package=gnome-bluetooth3&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=amd64&package=kodi&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=arm64&package=kodi&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=s390x&package=kodi&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=ppc64el&package=libnet-bluetooth-perl&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=arm64&package=pipewire&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=ppc64el&package=pipewire&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=s390x&package=pipewire&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=arm64&package=pulseaudio&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=i386&package=pulseaudio&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=s390x&package=pybluez&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=arm64&package=python-dbusmock&trigger=bluez%2F5.77-0ubuntu2
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&arch=arm64&package=ubertooth&trigger=bluez%2F5.77-0ubuntu2

1. https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2083131/comments/18
2. https://ubuntu-archive-team.ubuntu.com/proposed-migration/oracular/update_excuses.html#bluez

[Andreas Hasenack (ahasenack)]

These new test runs now passed and are green.

[Andreas Hasenack (ahasenack)]

The verification of the Stable Release Update for bluez has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package bluez - 5.77-0ubuntu2

---------------
bluez (5.77-0ubuntu2) oracular; urgency=medium

  * debian/patches/git-reconnect-fix.patch:
   - cherry pick an upstream fix to resolve reconnection problems for
     devices after a suspend or restart (lp: #2085162)

 -- Sebastien Bacher <email address hidden> Fri, 22 Nov 2024 11:10:16 +0100

[Sebastien Bacher (seb128)]

Would anyone who had the issue be able to do the verification on Noble?

[Andrew Skalski (askalski)]

I'd be happy to help test on Noble. I'm able to reproduce the issue reliably by restarting the bluetooth service, after which my bluetooth headset won't connect until I re-pair it.

I enabled noble-proposed but didn't find an updated bluez package there. What package should I test?

[One-Man-Bucket (erik-lindblad)]

I can also reliably repro the issue with a pair of bose qc ultra and noble!

I can test it later today if the package is available somewhere

[Sebastien Bacher (seb128)]

Sorry I got confused but it seems we didn't get the SRU for Noble published yet, I will work on that and post another update

[Yura Pakhuchiy (yura-p)]

> Would anyone who had the issue be able to do the verification on Noble?

I would be happy to test the fix for noble as well.

[Lasse Brandt Thomsen (bitmand)]

On 24.04 Noble and my Bose QC45 headphones won't reconnect after reboot.

Created a bluez package with a patched src/adapter.c using: https://launchpadlibrarian.net/757506303/bluez-fix-address.patch
(build instructions: https://gist.github.com/bitmand/76f7bd5cbb22cb51ef1e82db320eadc6 )

After installing it, my headphones connected without a problem. Rebooted computer and headphones connects perfectly fine - great patch! \o/

[Brendan_P (brendan-p)]

Any news on when the fix for Nobel will be released. Thanks for everyone's time and effort.

[Sebastian Unger (sebunger44)]

Same here. On Noble and quite happy to test the fix.

[Janne Hakonen (jhakonen)]

Followed bitmand's instructions with Kubuntu 24.04. After reboot, my Sony WH-1000XM3 headset connects perfectly. So fix seems to work. Thank you!

[Denis Franco (pumpkin-link)]

I confirm the bugfix from the patch works perfectly on Noble 24.04 on my WH-1000XM3 following bitmand gist instructions

[Robie Basak (racb)]

Hello Sitsofe, or anyone else affected,

Accepted bluez into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.72-0ubuntu5.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Robie Basak (racb)]

Thank you to those who have already tested the patch for Noble independently of Ubuntu's build of it. That gives us confidence that the patch is what we need.

Please note though that we also need to test the final proposed binary build of the fix, which will be available soon. Your further testing of this binary would be helpful and appreciated! See the previous comment for instructions.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted bluez (5.72-0ubuntu5.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libnet-bluetooth-perl/unknown (armhf)
network-manager/unknown (armhf)
pipewire/unknown (armhf)
pulseaudio/unknown (armhf)
pybluez/unknown (armhf)
ubertooth/unknown (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#bluez

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Harm van Bakel (hvbakel)]

I installed the bluez package from the proposed repository and my bluetooth audio devices are finally reconnecting again automatically after a reboot.

[Andrew Skalski (askalski)]

I haven't seen the package yet after enabling proposed, but I assume that has something to do with the armhf failures.

So I manually downloaded the bluez package from the launchpad page and installed it on my laptop. It's working perfectly. My bluetooth headphones connect reliably again after waking the laptop up from sleep, across reboots, and after "service bluetooth restart".

My desktop is still running the old bluez package, so I can retest once the armhf build issues have been resolved.

[Harm van Bakel (hvbakel)]

@askalski: this could be due to the change in procedure for installing packages from the proposed repository since Noble. After enabling the pre-release updates in the 'Developer options' tab of 'Software & updates', enter the following on the command line to selectively install the bluez package:

sudo apt install -t noble-proposed bluez

This will install the package and its dependencies from proposed.

[Andrew Skalski (askalski)]

Thanks. The "-t noble-proposed" did the trick.

I tested on my desktop (rebooting & service bluetooth restart) and the headphones are connecting properly again. Everything seems to be working as it should.

[Daniel van Vugt (vanvugt)]

Noble verification done per comments #29 and #32.

The armhf autopkgtest failures seem to be unrelated. Looks like a temporary armhf infrastructure problem.

[Mikk Kiilaspää (mikk-folderit)]

I can also confirm that the version 5.72-0ubuntu5.1 fixed the auto-reconnect for my Oneplus Nord Buds.
They now reconnect after resume from sleep and also when switching between devices with a long-press on the headphones (between my phone and laptop).

[Launchpad Janitor (janitor)]

This bug was fixed in the package bluez - 5.72-0ubuntu5.1

---------------
bluez (5.72-0ubuntu5.1) noble; urgency=medium

  * Add git-reconnect-fix.patch to resolve reconnection problems for
    devices after a suspend or restart (LP: #2085162)

 -- Daniel van Vugt <email address hidden> Tue, 25 Feb 2025 14:11:15 +0800

[Denis Franco (pumpkin-link)]

Sorry for the bump but for anyone like me who built the package locally using bitmand's gist, I had to use the following command to force a "downgrade" from the automatically generated patch number "-ubuntu6" to the official "-ubuntu-5.1":
```
sudo apt install bluez=5.72-0ubuntu5.1
```
(Confirmed the official package works for me too, by the way)

[astroscion (astroscion)]

Since a few days ago, I'm again experiencing issues with Bluetooth not waking up after suspend.

I'm running:
    Bluez version: 5.72-0ubuntu5.1
    Kernel: 6.11.0-26-generic
    Session: Both X11 and Wayland

Please let me know if you need logs or any additional information.

[Daniel van Vugt (vanvugt)]

This bug is closed. I suggest subscribing to bug 2092158 instead, and you can try the proposed fix for that at:

  https://launchpad.net/ubuntu/+source/bluez/5.72-0ubuntu5.3/+build/30919292

Users of kernel 6.14 may also be experiencing bug 2113469.

[astroscion (astroscion)]

Thank you for bringing this to my attention. I hadn't noticed these tickets.
Kind regards,
Guillaume

Le 20/06/2025 à 03:35, Daniel van Vugt a écrit :
> This bug is closed. I suggest subscribing to bug 2092158 instead, and
> you can try the proposed fix for that at:
>
> https://launchpad.net/ubuntu/+source/bluez/5.72-0ubuntu5.3/+build/30919292
>
> Users of kernel 6.14 may also be experiencing bug 2113469.
>