Due to a regression in Bluez 5.71 devices that previously paired perfectly fine no longer can pair. When looking at journalctl you will see errors such as the following: bluetoothd[592]: Failed to load link keys for hci0: Invalid Parameters (0x0d) This issue has already been reported at https://github.com/bluez/bluez/issues/686 and fixed by https://github.com/bluez/bluez/commit/7ad5669402c9acff8e4cc808edc12a41df36654e. Applying this patch on top of Bluez 5.71 resolves the pairing issue. When unpatched not only does it cause pairing issues on Linux, but some devices get into an inconsistent state and can't pair on Windows anymore when sharing the same pairing key (1). [1] https://wiki.archlinux.org/title/Bluetooth#Dual_boot_pairing Reproducible: Always Steps to Reproduce: 1. Turn on device previously paired over Bluetooth 2. Click connect in GNOME Bluetooth settings to initiate a connection Actual Results: It either connects and then immediately disconnects or doesn't connect at all. Expected Results: The device should remain connected and allow the device to be used (ex: play audio). It would be appreciated if this patch already upstreamed can be applied to the Fedora package. I have applied this patch to my local build of the bluez package and the issue has been resolved.
My problem is related. bluez-5.70-5.fc39.x86_64 is work, but bluez-5.71-1.fc39.x86_64 can't connecting to my Panasonic SA-PMX80 micro hifi device.
Same here, has problems connecting to all my Bluetooth devices via KDE or using bluetoothctl. The patch described above fixes it.
*** This bug has been marked as a duplicate of bug 2255295 ***