Created attachment 1484238 [details] sosreport In the kernel-4.17.19-200.fc28.x86_64 kernel package version, the mouse pointer works normally, But mouse pointer does not move for kernel-4.18.7-200.fc28.x86_64 and kernel-4.18.5-200.fc28.x86_64 version. I have found that when a device is connected in /var/log/message, the message is different from the previous one as below, @kernel-4.17.19-200.fc28.x86_64 .... [ 76.276983] usb 2-3.4.3: USB disconnect, device number 9 [ 77.487323] usb 2-3.4.3: new full-speed USB device number 15 using xhci_hcd [ 77.579281] usb 2-3.4.3: New USB device found, idVendor=047d, idProduct=8018, bcdDevice= 1.02 [ 77.579305] usb 2-3.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 77.579307] usb 2-3.4.3: Product: Expert Wireless TB [ 77.579309] usb 2-3.4.3: Manufacturer: Kensington [ 77.588823] input: Kensington Expert Wireless TB as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.4/2-3.4.3/2-3.4.3:1.0/0003:047D:8018.0009/input/input29 <---- (1) [ 77.641514] hid-generic 0003:047D:8018.0009: input,hidraw3: USB HID v1.11 Mouse [Kensington Expert Wireless TB] on usb-0000:00:14.0-3.4.3/input0 [ 77.642928] hid-generic 0003:047D:8018.000A: hiddev98,hidraw4: USB HID v1.10 Device [Kensington Expert Wireless TB] on usb-0000:00:14.0-3.4.3/input1 @kernel-4.18.7-200.fc28.x86_64, kernel-4.18.5-200.fc28.x86_64 ... [ 220.388554] usb 2-3.4.3: USB disconnect, device number 9 [ 221.341095] usb 2-3.4.3: new full-speed USB device number 15 using xhci_hcd [ 221.435227] usb 2-3.4.3: New USB device found, idVendor=047d, idProduct=8018, bcdDevice= 1.02 [ 221.435228] usb 2-3.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 221.435229] usb 2-3.4.3: Product: Expert Wireless TB [ 221.435230] usb 2-3.4.3: Manufacturer: Kensington [ 221.445099] input: Kensington Expert Wireless TB Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.4/2-3.4.3/2-3.4.3:1.0/0003:047D:8018.0009/input/input37 <---- (1) [ 221.445177] input: Kensington Expert Wireless TB Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.4/2-3.4.3/2-3.4.3:1.0/0003:047D:8018.0009/input/input38 <---- (2) [ 221.445215] input: Kensington Expert Wireless TB Consumer Control as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.4/2-3.4.3/2-3.4.3:1.0/0003:047D:8018.0009/input/input39 <---- (3) [ 221.498152] hid-generic 0003:047D:8018.0009: input,hidraw3: USB HID v1.11 Mouse [Kensington Expert Wireless TB] on usb-0000:00:14.0-3.4.3/input0 [ 221.499326] hid-generic 0003:047D:8018.000A: hiddev98,hidraw4: USB HID v1.10 Device [Kensington Expert Wireless TB] on usb-0000:00:14.0-3.4.3/input1 How reproducible: Always, Updated latest kernel package and Kensington Expert Wireless TB Mouse. Steps to Reproduce: 1. Attached Kensington Expert Wireless TB Mouse 2. Updated latest kernel package Actual results: USB mouse point does not move the pointer in X window enviroment(Gnome). Expected results: I'm attached sosreport-csongwork-2018-09-18-ncaeatw.tar.xz file on this bugzilla. The checksum is: e450559bb3c9233c249cab3fc0cea78d BR/Leo
Please test 4.18.8, there were known HID fixes https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20
Hello Laura Thank you very much for your advice, I try to test 4.18.8-200.fc28.x86_64, it's works for me on T450s. I will update comment on https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20. BR/Leo
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.