After upgrading to bluez-5.81-1.fc42 Bluetooth is not working, cannot be turned on, as default adapter cannot be recognized Hardware Lenovo P1 gen7 Workaround is to downgrade to bluez-5.80-1.fc42 Reproducible: Always
Same here on MSI MAG X870E Tomahawk with Qualcomm Fastconnect 7800 WiFi/Bluetooth
> Hardware Lenovo P1 gen7 What is the actual BT HW, what devices are you connecting, also please add kernel/linux-firmware details.
Bluetooth: Device-1: Intel driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:9 chip-ID: 8087:0036 class-ID: e001 Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.4 lmp-v: 13 status: discoverable: no pairing: no class-ID: 7c010c and I guess, it is: Bluetooth: hci0: Found device firmware: intel/ibt-0291-0291.sfi
Same issue, interesting founding is that my bluetooth keyboard is actually working, indicating that Bluetooth is actually working but somehow the daemon failed to report to user process like bluetoothctl $ journalctl -b 0 -k --output=cat| grep blue -i Bluetooth: Core ver 2.22 NET: Registered PF_BLUETOOTH protocol family Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized Bluetooth: hci0: Device revision is 0 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is enabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 Bluetooth: hci0: DSM reset method type: 0x00 Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi Bluetooth: hci0: Boot Address: 0x100800 Bluetooth: hci0: Firmware Version: 200-48.24 Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 1372868 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 15420 usecs Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware timestamp 2024.48 buildtype 1 build 81864 Bluetooth: hci0: Firmware SHA1: 0xc115e35a Bluetooth: hci0: Fseq status: Success (0x00) Bluetooth: hci0: Fseq executed: 00.00.02.41 Bluetooth: hci0: Fseq BT Top: 00.00.02.41 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP socket layer initialized Bluetooth: MGMT ver 1.23 hid-generic 0005:1A81:1311.000F: input,hidraw8: BLUETOOTH HID v0.43 Keyboard [ikbc Keyboard] on c4:d0:e3:d7:cd:95 Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 $ journalctl -b 0 -u bluetooth.service --output=cat Starting bluetooth.service - Bluetooth service... bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Bluetooth daemon 5.81 Started bluetooth.service - Bluetooth service. Starting SDP server Bluetooth management interface 1.23 initialized Battery Provider Manager created src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution $ bluetoothctl list [empty output]
additional information: $ rpm -q kernel linux-firmware kernel-6.14.0-63.fc42.x86_64 linux-firmware-20250311-1.fc42.noarch $ lsusb | grep blue -i Bus 003 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
(In reply to Qiyu Yan from comment #4) > Same issue, interesting founding is that my bluetooth keyboard is actually > working, indicating that Bluetooth is actually working but somehow the > daemon failed to report to user process like bluetoothctl I have a fix in process, it looks to be an issue with dbus side of things. Update soon.
FEDORA-2025-99ba5bbe50 (bluez-5.81-2.fc41, iwd-3.5-1.fc41, and 1 more) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-99ba5bbe50
FEDORA-2025-7eed2de81a (bluez-5.81-2.fc42, iwd-3.5-1.fc42, and 1 more) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-7eed2de81a
FEDORA-2025-0749c0901e (bluez-5.81-2.fc40, iwd-3.5-1.fc40, and 1 more) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-0749c0901e
So I think bluez-5.81-2.fc4X should fix this, and it least fixes it for me across realtek/brcmfmac/iwlwifi HW that I can remotely access to test.
*** Bug 2356894 has been marked as a duplicate of this bug. ***
Fixed here with bluez-5.81-2.fc42 on hci_bcm4377 / apple silicon platforms
Qualcomm Fastconnect 7800 is also fixed with the -2 build, thanks
This looks bad enough to be at least an FE for final. (Affects my laptop too).
FEDORA-2025-99ba5bbe50 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-99ba5bbe50` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-99ba5bbe50 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-0749c0901e has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0749c0901e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0749c0901e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-7eed2de81a has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7eed2de81a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7eed2de81a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
the last build fixed for me too: Bluetooth: Device-1: Lite-On Wireless_Device driver: btusb v: 0.8 MediaTek Inc. - Lite-On Technology Corp.
It works, it's fixed.
(In reply to Adam Williamson from comment #14) > This looks bad enough to be at least an FE for final. (Affects my laptop > too). The problematic build was never stable so I'm confused why it would be a FE but that being said I believe/suspect it actually fixes some BT audio issues on the bluez that was stable so it's probably suitable for a FE.
ahh, that's my bad, I didn't notice the broken build never went stable. kparal mentioned the issue, I saw it looked bad and was also affecting my system, and I proposed it. Sorry. We can consider making this an FE for 'include fixed 5.81 in Final' though, indeed. Do you have any more details on the issues it fixes?
> We can consider making this an FE for 'include fixed 5.81 in Final' though, > indeed. Do you have any more details on the issues it fixes? I believe it fixes some MPRIS (BT input controls like vol +/- etc) issues (see #2332989)
Discussed during the 2025-04-07 blocker review meeting [1]: * AGREED: 2356863 - Rejected FinalFreezeException - The broken version was never stable, and thus this update doesn't present any strong reason why it needs to be pushed through freeze. If such a reason appears, we can reconsider the vote. [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-04-07/f42-blocker-review.2025-04-07-16.01.log.html
FEDORA-2025-99ba5bbe50 (bluez-5.81-2.fc41, iwd-3.6-1.fc41, and 1 more) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-7eed2de81a (bluez-5.81-2.fc42, iwd-3.6-1.fc42, and 1 more) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-0749c0901e (bluez-5.81-2.fc40, iwd-3.6-1.fc40, and 1 more) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.