You are not logged in.
Hi All,
after updating to GNOME 42 yeterday, I noticed that my bluetooth mouse no longer works. My first steps of troubleshooting showed that the USB BT transceiver I'm using
Bus 001 Device 025: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x8771
bcdDevice 2.00
iManufacturer 1 Realtek
iProduct 2 Bluetooth Radio
was not powered on. Running
power on
in bluetoothctl, I got
Failed to set power on: org.bluez.Error.Failed
at first and
Failed to set power on: org.bluez.Error.Busy
for each consecutive attempt. I found out (by accident) that for some reason this will most of the time work when I plug it into another USB port which seems strange.
This works:
lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
|__ Port 6: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 7: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 21, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 4: Dev 21, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 10: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
This doesn't:
lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
|__ Port 6: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 7: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 22, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 22, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 10: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
which doesn't make sense to me as both ports are connected to the same physical connector on the mainboard. Also, it's always the same port that works. Moreover, both used to work fine before, and somehow I suspect the new gnome-bluetooth-3.0 package to have something to do with this - which is what was installed yesterday. Any ideas how to fix this? (The one thing that wasn't updated yesterday was the linux kernel package.)
Thanks in advance for your help!
Cheers,
Smoerrebroed
Last edited by Smoerrebroed (2022-04-30 05:16:51)
Offline
FWIW, the BT settings in GNOME do not work either. I cannot turn on (or off) BT which - again - was working previously.
Offline
Alright, some more discoveries:
It looks like after some playing around with it, my existing BT transceiver no longer works in one of the USB ports, starting with installation of the most recent update to
gnome-bluetooth-3.0
as far as I can tell. (
gnome-bluetooth
has been removed already). This, however, is not related to the transceiver or the USB port being broken as both work using a different device.
This is the port that doesn't work:
$ lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
|__ Port 6: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 7: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 9: Dev 9, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 9: Dev 9, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 10: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
I find this curious as it is actually a less nested path which should normally cause less issues. Any ideas what might be causing this?
EDIT
Some more findings: When force-removing by using
pacman -Rdd gnome-bluetooth-3.0
The transceiver starts working again like before. Unfortunately, this breaks GNOME or at least gdm.
Moreover, I discovered that I can only make the transceiver work reliably in other USB ports by setting
AutoEnable=true
in
/etc/bluetooth/main.conf
Still looking for some advice as to what could bring back functionality on the USB port used previously - or what would stop the new BT package from meddling with it.
Last edited by Smoerrebroed (2022-04-15 06:04:03)
Offline
Looks like this was fixed by (one of the) recent updates. Not exactly sure what caused it, but now things are back to normal.
Offline