1. Please describe the problem: I can no longer connect to my Bluetooth mouse and keyboard. Toggling the checkbox in GNOME Bluetooth does nothing. 2. What is the Version-Release number of the kernel: kernel-6.11.4-300.fc41.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Works on 6.11.3-300.fc41.x86_64. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Happened on two consecutive boots. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Didn't try. 6. Are you running any modules that not shipped with directly Fedora's kernel?: Yes, zenpower. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. I will, I also have this in the bluetoothd logs: bluetoothd[1264]: Failed to set mode: Busy (0x0a) Reproducible: Always
Created attachment 2052691 [details] dmesg
This should be fixed by the fixes from the latest bluetooth pull-request, see this email from Thorsten, the kernel regression tracker: https://lore.kernel.org/regressions/4e1977ca-6166-4891-965e-34a6f319035f@leemhuis.info/ Thorsten is pushing for these to get merged and backported ASPA, but maybe we should carry these as downstream patches in Fedora for now ?
yes on carry these as downstream patches in Fedora , my bluetooth mouse it is also broke
FEDORA-2024-9862e2555a (kernel-6.11.4-201.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-9862e2555a
FEDORA-2024-93ed69b6d4 (kernel-6.11.4-101.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-93ed69b6d4
FEDORA-2024-b1092ef4d5 (kernel-6.11.4-301.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-b1092ef4d5
FEDORA-2024-93ed69b6d4 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-2024-93ed69b6d4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-93ed69b6d4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-9862e2555a 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-2024-9862e2555a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9862e2555a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-b1092ef4d5 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-2024-b1092ef4d5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b1092ef4d5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I can confirm that kernel-6.11.4-301.fc41 fixes my Bluetooth issue.
FEDORA-2024-b1092ef4d5 (kernel-6.11.4-301.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-9862e2555a (kernel-6.11.4-201.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-93ed69b6d4 (kernel-6.11.4-101.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.