Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1898495
Summary: | Cannot activate bluetooth after kernel 5.9 update | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | michele.riva | ||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 33 | CC: | acaringi, adscvr, airlied, bskeggs, fhortner, hdegoede, itamar, jarodwilson, jeremy, jforbes, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, mjg59, mwc-250sav, ptalbert, rms, steved, trubonru | ||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | kernel-5.10.6-200.fc33 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2021-01-14 01:39:29 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
seems to be a kernel issue, since also other distros are affected. Seems to be an issue with the kernel trying to use Link-Layer Privacy for BLE devices see bugzilla.kernel.org: Bluetooth mouse Logitech M720 doesn't work: https://bugzilla.kernel.org/show_bug.cgi?id=209717 Bluetooth connection to Logitech MX Master 2S lost after each reboot: https://bugzilla.kernel.org/show_bug.cgi?id=209745 kenel patch already available: Bluetooth: Fix: LL PRivacy BLE device fails to connect: https://patchwork.kernel.org/project/bluetooth/patch/20201022082304.31757-1-sathish.narasimman@intel.com/ also known at ArchWiki: https://wiki.archlinux.org/index.php/Bluetooth#Problems_with_all_BLE_devices_on_kernel_5.9+ *** This bug has been marked as a duplicate of bug 1897038 *** Actually, I can't even reach the pairing step thus it might be something related, yet different. Gnome's control panel simply shows that bluetooth is turned off, event though the switch on the top right corner is on, thus no device is listed (and probably not even scanned). I confirm this bug is NOT solved by kernel 5.9.9-200.fc33 from https://bodhi.fedoraproject.org/updates/FEDORA-2020-febe24a7ca This is a different issue than bluetooth pairing. Created attachment 1731420 [details]
Screenshot of issue in Gnome control panel
I can also confirm that kernel 5.9.9-200.fc33 *DOES NOT* fix this problem -- it still remains (bluetooth is completely disabled). This bug is NOT a duplicate of 1897038 - it has nothing to do with pairing. Please reopen this bug. Returning to 5.8.18-300.fc33 restores bluetooth functionality. I'm using the KDE spin. This problem has been fixed upstream: FS#68749 - [linux] Bluetooth not working with rtl8822ce kernel 5.9.x https://bugs.archlinux.org/task/68749 michele, can you reopen this bug as submitter? I want to make sure that any realtek bluetooth adapter users see this. Thanks. bugzilla.kernel.org: Bug 210453 - [BISECTED] rtl8822cu device : "Bluetooth : No device found" Fix confirmed in kernel.org linux-next. I have added this patch to the stabilization tree. It will be in kernels beginning with 5.10.6. FEDORA-2021-3465ada1ca has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3465ada1ca FEDORA-2021-3465ada1ca has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3465ada1ca` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3465ada1ca See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-3465ada1ca has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. I don't think this caught all the recent bluetooth issues... # uname -srvmpio Linux 5.10.7-200.fc33.x86_64 #1 SMP Tue Jan 12 20:20:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I need to reboot in order to be able to reconnect to my bluetooth headset. Sorry, reconnect is not the correct term, it connects, it's just that the sound profile never gets set to a2dp. pactl info Server String: /run/user/xxx/pulse/native Library Protocol Version: 34 Server Protocol Version: 34 Is Local: yes Client Index: 8 Tile Size: 65472 User Name: xxx Host Name: xxxx Server Name: pulseaudio Server Version: 14.0-rebootstrapped Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: bluez_sink.E8_07_BF_33_5A_30.a2dp_sink Default Source: alsa_input.pci-0000_00_1f.3.analog-stereo Cookie: fd4b:0ee8 But the sound still comes from the laptop's speakers. After reboot, first connection $ pactl info Server String: /run/user/xx/pulse/native Library Protocol Version: 34 Server Protocol Version: 34 Is Local: yes Client Index: 8 Tile Size: 65472 User Name: xx Host Name: xx Server Name: pulseaudio Server Version: 14.0-rebootstrapped Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-0000_00_1f.3.analog-stereo Default Source: alsa_input.pci-0000_00_1f.3.analog-stereo Cookie: 525f:85d3 Unsure of how to specify by command, I go to the Gnome Shell's sound settings, verify that it says "speakers" and specify the proper headset output device... $ pactl info Server String: /run/user/xx/pulse/native Library Protocol Version: 34 Server Protocol Version: 34 Is Local: yes Client Index: 11 Tile Size: 65472 User Name: xx Host Name: xx Server Name: pulseaudio Server Version: 14.0-rebootstrapped Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: bluez_sink.E8_07_BF_33_5A_30.a2dp_sink Default Source: alsa_input.pci-0000_00_1f.3.analog-stereo Cookie: 525f:85d3 BUT the sound still comes from speakers. I'm going two kernels backward to kernel-core-5.9.13-200.fc33.x86_64 in order to check if it works better. Nopes, same behaviour. Ah... it seems that the gnome shell settings application is sending the test to the speakers, but sound is indeed coming from the headset! confusing for users, though. very confusing. I can confirm this bug. Device succsessfully connect to my wireless headset (Headset play a sound that signalaize that device is connected). But sound still goes from laptop speakers. there is also no sound profile for headset in my gnome sound settings Fedora 34 on my HP laptop Kernel version: 5.11.6-300.fc34.x86_64 |
Created attachment 1730086 [details] Dmesg since boot 1. Please describe the problem: After upgrading a fresh install of Fedora 33 (kernel 5.8.15-301) to kernel 5.9.8-200, triggering the bluetooth on/off switch in both the control center and the applet does not have any effect. 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``: Did not test yet 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 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. See attached dmesg.txt