Hide Forgot
Description of problem: With kernel-4.0.8-300.fc22.x86_64 bluetooth works fine, but with either kernel-4.1.2-200.fc22.x86_64 or kernel-4.1.3-200.fc22.x86_64, bluetooth on my macbook is broken in GNOME Version-Release number of selected component (if applicable): kernel-4.1.2-200.fc22.x86_64 kernel-4.1.3-200.fc22.x86_64 How reproducible: 100% Steps to Reproduce: 1. Update to kernel-4.1.2-200.fc22.x86_64 2. Try to connect bluetooth device (e.g. mouse) 3. Notice that bluetooth settings in GNOME shell seems broken Actual results: Bluetooth settings dialog is not listing devices, device does not connect automatically Expected results: Previously paired device connects automatically; devices in range are shown in dialog. Additional info: I think changing of screen brightness may also be affected by this update, but I haven't had a chance to verify that yet.
Here's some dmesg output related to Bluetooth: [grdryn@redhat ~]$ dmesg -k | grep Bluetooth [ 2.490166] usb 1-8.3: Product: Bluetooth USB Host Controller [ 10.746302] Bluetooth: Core ver 2.20 [ 10.746424] Bluetooth: HCI device and connection manager initialized [ 10.746426] Bluetooth: HCI socket layer initialized [ 10.746428] Bluetooth: L2CAP socket layer initialized [ 10.746435] Bluetooth: SCO socket layer initialized [ 10.752110] Bluetooth: hci0: BCM: Read verbose config info failed (-16) [ 10.897048] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.897050] Bluetooth: BNEP filters: protocol multicast [ 10.897053] Bluetooth: BNEP socket layer initialized ^It was the "hci0: BCM: Read verbose config info failed (-16)" that shows up in red that made me think of providing this info. Let me know if there's any other info that you would like me to provide.
Looks like bug has been identified in upstream: https://bugzilla.kernel.org/show_bug.cgi?id=100651 Perhaps someone could apply the patch/build kernel package for us to test?
(In reply to Kristjan Kullerkann from comment #2) > Looks like bug has been identified in upstream: > https://bugzilla.kernel.org/show_bug.cgi?id=100651 > > Perhaps someone could apply the patch/build kernel package for us to test? If I read the bug correctly, it was included in upstream 4.1.4. We have that built and in updates-testing already. You should be able to test it from there and let us know.
Sorry, I'm unable to find 4.1.4 in updates-testing. It hasn't been staged yet?
Never mind, found it: https://admin.fedoraproject.org/updates/kernel-4.1.4-200.fc22?_csrf_token=6ef7cba4bc74cb731bb96312542a36026891a8aa It's fixed in 4.1.4, thank you!
kernel-4.1.4-200.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/kernel-4.1.4-200.fc22
kernel-4.1.4-100.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/kernel-4.1.4-100.fc21
Package kernel-4.1.4-200.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-4.1.4-200.fc22' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12908/kernel-4.1.4-200.fc22 then log in and leave karma (feedback).
kernel-4.1.4-200.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
kernel-4.1.4-100.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.