Bluetooth mouse stops working immediately after ALMA-8.10 installation

Short, sweet, and to the point. It is a bluetooth mouse with a USB-wireless dongle/adapter.

Does anyone have any ideas?

Is it a connected with Bluetooth or USB HID.
Any info /error in journalctl about bluetooth or USB.
You could unplug the USB and but it back in to trigger some logs.
Hopefully they indicate some source of the problem.
In the case the dongle is connected to a USB 3.0 port try and 2.0 port if available.

1 Like

@rvk, thanks for replying. I don’t know how to use journalctl to target this problem; however, I executed journalctl -f on its own then plugged in the usb adapter. This is not a bluetooth mouse afterall. Good catch.

Anyway, the results I see from journalctl are the following: I skipped the hostname,dates,time

kernel: usb 1-2: new full-speed USB device number 6 using xhci_hcd
kernel: usb 1-2: New USB device found, idVendor=046d, idProduct=c52f, bcdDevice=30.00
kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 1-2: Product: USB Receiver
kernel: usb 1-2: Manufacturer: Logitech
kernel: usb 1-2: Device is not authorized for usage
kernel: sdhci-pci 0000:00:12:0 SDHCI controller found [8086:2296] (rev 21)
mtp-probe[3885]: checking bus 1, device 6: “/sys/devices/pci0000:00:14.0/usb1/1-2”
mtp-probe[3885]: bus: 1, device: 6 was not an MTP device
fwupd[2995]: 21:59:35:0221 FuEngine failed to probe device usb:00:02: USB error on device 046d:c52f : Entity not found [-5]
upowerd[2231]: unhandled action ‘bind’ on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2
kernel: usb 1-2: USB disconnect, device number 6
upowerd[2231]: unhandled action ‘unbind’ on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2

@rvk, thanks for the tip on journalctl, I barely know how to use it in various contexts. :frowning_face:

However, posting the error enabled me to do a man on the error: Device is not authorized for usage.

With that I found an article on StackExchange Device is not authorized for usage, wasn’t sure if I should trust it because it isn’t a RHEL variant, but it did work for me.

Thanks for the tip @rvk!

Glad to here you found a solution.