Bug 1512167

Summary:	Thinkpad Yoga 260 trackpoint is too slow even with maxed out speed setting
Product:	[Fedora] Fedora	Reporter:	ell1e <el>
Component:	libinput	Assignee:	Peter Hutterer <peter.hutterer>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	27	CC:	dchen, el, peter.hutterer
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-19 00:41:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ell1e 2017-11-11 04:59:14 UTC

Description of problem:
Thinkpad Yoga 260 trackpoint is too slow even with maxed out speed setting. At the maximum setting, it's barely usable and ok for occasional use but risking pain and health effects for prolonged use. (In case this is relevant, I'm testing this under a GNOME 3 Xorg session due to https://bugzilla.redhat.com/show_bug.cgi?id=1397898 ) 

Due to the recent changes in libinput trackpoint handling ( https://bugs.freedesktop.org/show_bug.cgi?id=100982 ) I'm not sure what I need to do to fix this.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Use Thinkpad Yoga 260 & Fedora 27
2. Start GNOME 3 Xorg session
3. Open settings, go to Devices > Mouse & Touchpad and max out mouse speed and try to use mouse pointer

Actual results:
too slow

Expected results:
faster than required (since obviously maxed out speed should have some buffer for people who like it extremely fast)

Additional info:

Comment 1 ell1e 2017-11-11 04:59:38 UTC

Version-Release number of selected component (if applicable):
libinput-1.9.0-1.fc27.src.rpm

Comment 2 Peter Hutterer 2017-11-13 00:48:15 UTC

see bug 1509017 for the data I need (libinput measure trackpoint-range), thanks

Comment 3 Peter Hutterer 2017-12-19 00:41:29 UTC


*** This bug has been marked as a duplicate of bug 1509017 ***

Comment 4 ell1e 2017-12-26 10:52:12 UTC

jonas@cyberman:~$ libinput measure trackpoint-range
libinput: measure is not a libinput command or not installed. See 'libinput --help'

The bug you marked this a duplicate off says the trackpoint speed is too fast, however on this model it is _extremely too slow_ - barely usable at max speed.

Comment 5 ell1e 2018-01-08 07:36:22 UTC

It seems I was on an old libinput version. I updated now and the speed is nice! So it was too slow simply because I hadn't been shipped the upgrade which revamps all the code yet.