I have a system with which I use a Lenovo USB keyboard with a trackpoint pointer -- the little red eraser mouse, as seen on the laptops. I hadn't updated this system in a while (I admit; bad, I know) and applied a big batch of updates (including from updates testing). Now, whenever I touch the pointer stick, the cursor jumps to the top left corner (0,0) and can't be moved from there. I plugged in an external mouse and that looks fine. The `libinput list-devices` command shows:
Device: Lenovo ThinkPad Compact USB Keyboard with TrackPoint Kernel: /dev/input/event10 Group: 8 Seat: seat0, default Capabilities: keyboard pointer Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: disabled Nat.scrolling: disabled Middle emulation: disabled Calibration: n/a Scroll methods: *button Click methods: none Disable-w-typing: n/a Accel profiles: flat *adaptive Rotation: n/a
There was a kernel update, but going back to an older version doesn't solve it. I'm on Xorg on this system.
Any idea what might be going on, and what I can do about it? And, what recent update might have caused this?
On 05/30/2018 09:40 AM, Matthew Miller wrote:
Device: Lenovo ThinkPad Compact USB Keyboard with TrackPoint Kernel: /dev/input/event10
Any idea what might be going on, and what I can do about it? And, what recent update might have caused this?
Try installing "evtest" and run "evtest /dev/input/event10". Check that the device features are correct. Move the pointer and see if the output looks reasonable.
On Wed, May 30, 2018 at 11:23:48AM -0700, Samuel Sieb wrote:
Try installing "evtest" and run "evtest /dev/input/event10". Check that the device features are correct. Move the pointer and see if the output looks reasonable.
Hmmm. I'm seeing events like
Event: time 1527709749.694295, -------------- SYN_REPORT ------------ Event: time 1527709749.702370, type 2 (EV_REL), code 1 (REL_Y), value -14 Event: time 1527709749.702370, -------------- SYN_REPORT ------------ Event: time 1527709749.718310, type 2 (EV_REL), code 1 (REL_Y), value -12 Event: time 1527709749.718310, -------------- SYN_REPORT ------------ Event: time 1527709749.734368, type 2 (EV_REL), code 1 (REL_Y), value -10 Event: time 1527709749.734368, -------------- SYN_REPORT ------------ Event: time 1527709749.750295, type 2 (EV_REL), code 1 (REL_Y), value -9 Event: time 1527709749.750295, -------------- SYN_REPORT ------------ Event: time 1527709749.766365, type 2 (EV_REL), code 1 (REL_Y), value -5 Event: time 1527709749.766365, -------------- SYN_REPORT ------------ Event: time 1527709749.782306, type 2 (EV_REL), code 0 (REL_X), value 1 Event: time 1527709749.782306, type 2 (EV_REL), code 1 (REL_Y), value -7
which seem to correspond to the direction I'm pressing. Yet the cursor stays stuck up at 0,0.
On Wed, May 30, 2018 at 12:40:54PM -0400, Matthew Miller wrote:
There was a kernel update, but going back to an older version doesn't solve it. I'm on Xorg on this system. Any idea what might be going on, and what I can do about it? And, what recent update might have caused this?
Annnd --- downgrading libinput to 1.10.7 from 1.10.901 fixes the problem. I see libinput was just rebuilt to 1.11 while I was diagnosing that and the update isn't out yet, so I'm off to test that.
On Wed, May 30, 2018 at 04:04:46PM -0400, Matthew Miller wrote:
There was a kernel update, but going back to an older version doesn't solve it. I'm on Xorg on this system. Any idea what might be going on, and what I can do about it? And, what recent update might have caused this?
Annnd --- downgrading libinput to 1.10.7 from 1.10.901 fixes the problem. I see libinput was just rebuilt to 1.11 while I was diagnosing that and the update isn't out yet, so I'm off to test that.
And for the record, this was a regression in libinput, at least one other person was seeing it, and we think we have a fix. https://bugzilla.redhat.com/show_bug.cgi?id=1583324
Thanks to Peter Hutterer for quick work on this!
-
Matthew Miller -
Samuel Sieb