Created attachment 1570404 [details]
Output of journalctl --no-hostname -k > dmesg.txt
1. Please describe the problem:
Bluetooth is not working at all in current (5.0.16-100.fc28.x86_64) kernel on a bog-standard lenovo yoga 900. failing from the first reboot after updating . It was working perfectly in 5.0.9-100.fc28.x86_64. Bluetooth is still working perfectly when booted to windows 10 (i.e. it doesn't seem to be a hardware issue). I will attach lsusb -v output after submitting this report.
I'm sorry, I won't be able to give much further feedback. I have arthritis that makes using the trackpad very painful. I will have to revert to kernel 5.0.9-100.fc28.x86_6 as soon as I finish this report, so that I can resume using the bluetooth mouse.
2. What is the Version-Release number of the kernel:
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
Yes. Just appeared in 5.0.16-100.fc28.x86_64
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
Yes. Just reboot. Never works.
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``:
Sorry, this is my primary work machine, I can't risk experimenting with it.
6. Are you running any modules that not shipped with directly Fedora's kernel?:
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.
Created attachment 1570405 [details]
Output and Standard Error from running lsusb -v
Apologies, please read all references to the preceding (working) kernel in the initial report as being to 5.0.13-100.fc28, rather than to 5.0.9-100.fc28 (I'd edit the report if I could find a way, but I'm guessing it's read-only to preserve the history trace).
It seems it's not easy to revert a kernel update, so I'll just be booting to the previous kernel, meaning that I can relatively easily boot to 5.0.16-100.fc28.x86_64 if further detail is needed.
Also, it's quite possible that this bug should be allocated to the kernel-modules package rather than the kernel, I'm sorry, I just don't know enough about the kernel/modules structure to figure out where the problem lies.
I confirm this problem.
description: USB controller
product: Sunrise Point-LP USB 3.0 xHCI Controller
vendor: Intel Corporation
physical id: 14
bus info: pci@0000:00:14.0
width: 64 bits
capabilities: pm msi xhci bus_master cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:125 memory:dfb10000-dfb1ffff
product: xHCI Host Controller
vendor: Linux 5.0.11-300.fc30.x86_64 xhci-hcd
physical id: 0
bus info: usb@1
logical name: usb1
configuration: driver=hub slots=12 speed=480Mbit/s
description: Bluetooth wireless interface
vendor: Intel Corp.
physical id: 8
bus info: usb@1:8
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
BT mouse Logitech M555b
Works fine with kernel 5.0.11
Does not connect with both kernel 5.0.16 and 5.1.3
I did bisect.
For me and in my BT configuration, last working kernel is 5.0.14.
According changelog, not working kernel 5.0.15 includes these changes:
Chen-Yu Tsai (1):
Bluetooth: hci_bcm: Fix empty regulator supplies for Intel Macs
Luiz Augusto von Dentz (1):
Bluetooth: Fix not initializing L2CAP tx_credits
Marcel Holtmann (1):
Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
Young Xiao (1):
Bluetooth: hidp: fix buffer overflow
This is the messages I get when I enabled BT then try to connect to my BT mouse using kernel 4.0.15:
mai 20 15:30:06 laptop.home systemd: Starting Load/Save RF Kill Switch Status...
mai 20 15:30:06 laptop.home systemd: Started Load/Save RF Kill Switch Status.
mai 20 15:30:06 laptop.home audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 20 15:30:11 laptop.home systemd: systemd-rfkill.service: Succeeded.
mai 20 15:30:11 laptop.home audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 20 15:30:46 laptop.home bluetoothd: Can't get HIDP connection info
mai 20 15:30:46 laptop.home bluetoothd: connect error: Device or resource busy (16)
mai 20 15:30:49 laptop.home bluetoothd: Can't get HIDP connection info
mai 20 15:30:55 laptop.home bluetoothd: connect error: Host is down (112)
mai 20 15:31:02 laptop.home bluetoothd: Can't get HIDP connection info
mai 20 15:31:02 laptop.home bluetoothd: connect error: Device or resource busy (16)
mai 20 15:31:14 laptop.home bluetoothd: Can't get HIDP connection info
mai 20 15:31:20 laptop.home bluetoothd: connect error: Host is down (112)
In previous message please read kernel 5.0.15. Apologizes.
I have probably the same issue as here. My bluetooth mouse stopped working correctly with the recent kernel 5.0.16. I tried with re-pairing it, but it worked only until I have left it not moving for a while. After that, it couldn't reconnect. Everything works ok on kernel 5.0.14.
I did not take care this bug has been opened for Fedora 28.
I my case, this bug occurs with same kernel releases but with Fedora 30.
The same for me.
Problem with my old BT 2.0 mouse is fixed by kernel 5.1.4 (available on koji at this time).
Thanks for your efforts.
I can confirm this bug, kernel 5.0.16 shows problems with my bt mice (controller is an Intel N 6235). Anyway, I've tested the patch you can find at https://email@example.com/T/#u and it seems to fix the issue. Tested with 5.0.17 packaged via fedpkg.
Oh, I forgot to tell os is a Fedora 30 x86_64 here.
Same problem here with an HP bluetooth mouse on an Elitebook 745 G5. Bluetooth does not connect with kernel 5.0.16 or 5.0.17 or 5.1.4.
5.0.14 is the last one that works.
I have same Problem with Fedora 30 latest Kernel, with following devices:
Controller: 0cf3:3005 Qualcomm Atheros Communications AR3011 Bluetooth
Mouse: Targus Bluetooth Mouse Model: AMB09US
Just as a remark.
I got small script to workaround the problem, and get it fastly connected again.
Maybe it helps once waiting for a solution.
bluetoothctl pair 00:02:76:30:EA:32
bluetoothctl trust 00:02:76:30:EA:32
bluetoothctl connect 00:02:76:30:EA:32 'this is the device address of my mouse
A list of device addresses you get issuing:
I guess the issue reported by Alex is about a different bug. The bug we're talking about just makes it impossible to pair a bt device that does not make use of an encryption key. It affects cheap devices. You just can't pair them by using bluetoothctl, I already tried that.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
Just wanted to add that Kernel 5.1.5 solved the bluetooth issues for me (Fedora 30).