Bug #17237

Cursor 'drifts' after using trackpoint, preventing trackpad use

Added by kdr4 2019-11-15 09:27:49 . Updated 2019-11-29 09:14:51 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This issue is unrelated to issue Bug #17235 but complements and exacerbates it. It has existed in every version of Tails I have used, so going back as far as 3.10 at least, and continues to exist in 4.0. I have not tried Troubleshooting mode for this issue. This issue is not exhibited in Windows 10 on the same device, so I guess it’s not a hardware problem.

Essentially, what happens is that the cursor will frequently continue to move in the direction of last movement after user interaction with the trackpoint (this is a Lenovo device) has ended. This ‘drift’ is very slow (perhaps one pixel per second) and often unnoticeable at a short distance. So long as this ‘drift’ is in motion the user cannot use the trackpad, for example to perform a ‘two-finger scroll’ in a webpage.

A somewhat reliable way to fix the drift is to move the trackpoint in the opposite direction to the ‘drift’, but as this can result in a new ‘drift’ in the new direction, this is not a guaranteed fix.

This issue combines with Bug #17235 to make user interaction with Tails quite a chore, actually, hopefully one or the other can be addressed in the near future.


Subtasks


History

#1 Updated by kdr4 2019-11-16 08:18:49

Sorry, I double-checked the situation in Windows 10 and it seems the cursor ‘drift’ is experienced there too, but not as often, so perhaps this is a hardware issue after all. I’ll contact Lenovo technical support and report back.

#2 Updated by intrigeri 2019-11-16 10:06:38

  • Category set to Hardware support

Similarly to Bug #17235, a WhisperBack report would help checking if there’s anything relevant in the logs. Now, even with a report, given this also happens on Windows (even if less often), I strongly doubt that this ticket will ever be actionable by Tails :/

#3 Updated by kdr4 2019-11-29 08:33:05

This turned out to be a hardware fault. Sorry. Please close this bug.

#4 Updated by intrigeri 2019-11-29 09:14:51

  • Status changed from New to Rejected

> This turned out to be a hardware fault. Sorry. Please close this bug.

Thanks for letting us know!