Here is my system
Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel
Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] driver: nvidia v: 440.100
Display: x11 server: X.Org 1.20.8 driver: modesetting,nvidia resolution: 1: 1920x1080 2: 1920x1080~144Hz
OpenGL: renderer: GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100
The issue is that whenever I move my cursor during kernel startup, the kernel fails to register my mouse - a logitech G305 wireless - as a libinput device. During the times when it is successful, this appears on dmesg:
[ 4.184987] logitech-djreceiver 0003:046D:C53F.0008: hidraw7: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-5/input0
[ 4.433958] logitech-djreceiver 0003:046D:C53F.0009: hiddev2,hidraw8: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-5/input1
[ 4.490386] logitech-djreceiver 0003:046D:C53F.000A: hiddev3,hidraw9: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-5/input2
[ 4.547208] logitech-djreceiver 0003:046D:C53F.000A: device of type eQUAD Lightspeed 1_1 (0x0d) connected on slot 1
[ 4.786308] logitech-hidpp-device 0003:046D:4074.000E: input,hidraw13: USB HID v1.11 Keyboard [Logitech G305] on usb-0000:00:14.0-5/input2:1
[ 11.720449] logitech-hidpp-device 0003:046D:4074.000E: HID++ 4.2 device connected.'
when I move my mouse during the startup process - only right before showing the log in screen, which is during the kernel bootup, this would happen:
[ 4.184987] logitech-djreceiver 0003:046D:C53F.0008: hidraw7: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-5/input0
[ 4.433958] logitech-djreceiver 0003:046D:C53F.0009: hiddev2,hidraw8: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-5/input1
[ 4.490386] logitech-djreceiver 0003:046D:C53F.000A: hiddev3,hidraw9: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-5/input2
this error results in lsusb displaying the adapter as detected, but the device will not show up on libinput or xinput.
taking out the receiver and plugging the receiver back in seems to cause it to register just fine. This bug only occurs during startup.