Bug 2440721

Summary: bluetooth fails to connect after updating to 5.86-3 (from 5.84-2)
Product: [Fedora] Fedora Reporter: Ben Boeckel <fedora>
Component: bluezAssignee: Peter Robinson <pbrobinson>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 43CC: bnocera, dwmw2, lihis, michel, ngompa13, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: bluez-5.87-1.fc44 bluez-5.87-2.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-07-07 00:50:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Boeckel 2026-02-18 18:58:42 UTC
I updated to bluez-5.86-3.fc43.x86_64 and Bluetooth started failing. Reverting to bluez-5.84-2.fc43.x86_64 works. The patch in -3 doesn't match the patch that actually closed the linked issue. However, after looking closer, I see that 5.84 probably has a lot more changes to 5.86 than the release update I thought it was.

In package:

https://src.fedoraproject.org/rpms/bluez/c/f5d00e43c516d84c42ceaeaf27e535b38436ae9b?branch=rawhide

Committed upstream:

https://github.com/bluez/bluez/commit/066a164a524e4983b850f5659b921cb42f84a0e0

Upon startup:

bluetoothd[1529]: Failed to set default system config for hci0

Upon connecting to headphones:

Feb 18 12:34:44 rotor kernel: input: Bose QC45 (AVRCP) as /devices/virtual/input/input29
Feb 18 12:34:44 rotor systemd-logind[1542]: Watching system buttons on /dev/input/event20 (Bose QC45 (AVRCP))
Feb 18 12:34:44 rotor bluetoothd[1529]: Disconnected from D-Bus. Exiting.
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aac
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aac
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/opus_g
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/opus_g
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/faststream
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/opus_05
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/opus_05
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 18 12:34:44 rotor bluetoothd[1529]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Feb 18 12:34:44 rotor bluetoothd[1529]: Battery Provider Manager destroyed
Feb 18 12:34:44 rotor bluetoothd[1529]: Stopping SDP server
Feb 18 12:34:44 rotor bluetoothd[1529]: Exit
Feb 18 12:34:44 rotor systemd[1]: bluetooth.service: Deactivated successfully.

When restarting, this error shows up:

Feb 18 12:34:44 rotor bluetoothd[7220]: Failed to set default system config for hci0
Feb 18 12:34:44 rotor bluetoothd[7220]: Failed to set privacy: Rejected (0x0b)

Reproducible: Always

Comment 1 Fedora Update System 2026-07-05 11:47:32 UTC
FEDORA-2026-a3298b621e (bluez-5.87-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a3298b621e

Comment 2 Fedora Update System 2026-07-05 11:47:35 UTC
FEDORA-2026-7f7d44651d (bluez-5.87-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7f7d44651d

Comment 3 Fedora Update System 2026-07-06 13:41:31 UTC
FEDORA-2026-a3298b621e has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-a3298b621e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a3298b621e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-07-06 14:00:00 UTC
FEDORA-2026-7f7d44651d has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-7f7d44651d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7f7d44651d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-07-07 00:50:51 UTC
FEDORA-2026-a3298b621e (bluez-5.87-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2026-07-09 01:26:50 UTC
FEDORA-2026-b3df983849 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-b3df983849`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b3df983849

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-07-12 00:59:27 UTC
FEDORA-2026-b3df983849 (bluez-5.87-2.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.