Bug 2255295 - Bluetooth devices no longer connect
Summary: Bluetooth devices no longer connect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 39
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gopal krishna tiwari
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2255481 2256277 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-19 23:03 UTC by Sam Bashton
Modified: 2024-01-02 01:20 UTC (History)
9 users (show)

Fixed In Version: bluez-5.71-2.fc39 bluez-5.71-2.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-31 02:27:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sam Bashton 2023-12-19 23:03:09 UTC
Since upgrading to bluez-5.71 Bluetooth headphones no longer connect.
This seems to be the same issue reported at https://github.com/bluez/bluez/issues/686

Systemd status:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Wed 2023-12-20 09:34:31 AEDT; 22min ago
       Docs: man:bluetoothd(8)
   Main PID: 9730 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76621)
     Memory: 1.1M
        CPU: 25ms
     CGroup: /system.slice/bluetooth.service
             └─9730 /usr/libexec/bluetooth/bluetoothd

Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/faststream
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/faststream_duplex
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink/opus_05
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/opus_05
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Dec 20 09:34:31 hal bluetoothd[9730]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Dec 20 09:34:31 hal bluetoothd[9730]: Failed to load link keys for hci0: Invalid Parameters (0x0d)

Reproducible: Always

Steps to Reproduce:
Try to connect Bluetooth headphones. Other device types may be affected, but I don't use any.
Actual Results:  
[bluetooth]# hci0 new_settings: powered bondable ssp br/edr le secure-conn cis-central cis-peripheral 
[bluetooth]# Agent registered
[bluetooth]# [CHG] Controller 10:B1:DF:AA:5C:82 Pairable: yes
[CHG] Device 00:09:A7:1E:4E:44 Connected: yes
[CHG] Device 00:09:A7:1E:4E:44 Connected: no


Expected Results:  
Connected correctly.

https://github.com/bluez/bluez/issues/686

Comment 1 Peter Robinson 2023-12-19 23:09:04 UTC
Does it work with bluez-5.70-5.fc39

Please at least report something vaguely useful like the NVR of bluez, kernel, linux-firmware and your local bluetooth controller.

This bug report is basically useless.

Comment 2 Sam Bashton 2023-12-20 00:33:51 UTC
I can confirm that downgrading from bluez-5.71-1.fc39.x86_64 to bluez-5.70-5.fc39 does resolve the problem.

Comment 3 Takehiko Abe 2023-12-21 02:58:18 UTC
I have the same problem with bluetooth headphone and bluez 5.71.

Applying the kernel patch mentioned in https://github.com/bluez/bluez/issues/686 fixes it for me. So it is likely that it is the same bug.

https://github.com/bluez/bluez/issues/686#issuecomment-1858751323
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=df24d38bc7acd546eebd5567ea2d41f8eb2d6afa

Comment 4 Fedora Update System 2023-12-29 15:53:12 UTC
FEDORA-2023-f85b2263e4 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f85b2263e4

Comment 5 Fedora Update System 2023-12-29 15:53:14 UTC
FEDORA-2023-d6652611eb has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d6652611eb

Comment 6 Peter Robinson 2023-12-29 16:40:16 UTC
*** Bug 2255481 has been marked as a duplicate of this bug. ***

Comment 7 Fedora Update System 2023-12-30 01:43:57 UTC
FEDORA-2023-d6652611eb has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d6652611eb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d6652611eb

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

Comment 8 Fedora Update System 2023-12-30 02:14:35 UTC
FEDORA-2023-f85b2263e4 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-f85b2263e4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f85b2263e4

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

Comment 9 Fedora Update System 2023-12-31 02:27:16 UTC
FEDORA-2023-d6652611eb has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Peter Robinson 2023-12-31 10:35:29 UTC
*** Bug 2256277 has been marked as a duplicate of this bug. ***

Comment 11 Fedora Update System 2024-01-02 01:20:56 UTC
FEDORA-2023-f85b2263e4 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.