[solved]Trackpoint behaviour changed after upgrade to libinput 1.9

markus21 · 2017-11-03 12:27:29

I have a strange situation going on here with my trackpoint on my Lenovo X1 Carbon G5.

As of late there was an update to libinput 1.9, that it increased sensitivity and speed of my trackpoint tremendously. I tried to figure it out by just looking into the wiki but there are some inconsitencies:

1. The gui tool doesn't allow me to control speed or sensitivity.

2. To change the attributes manually I think I have to find the right direcory to change them. Regarding the wiki they should be either in

/sys/devices/platform/i8042/serio1/serio2/ or /sys/devices/platform/i8042/serio1/serio3/ .

However I only have serio0 and serio1

BUT: Inside of /serio1 there is /serio2 so it looks like this

[markus@X1_Carbon]: ~>$ ls /sys/devices/platform/i8042/serio0/
bind_mode  description  driver  drvctl  err_count  extra  firmware_id  force_release  id  input  modalias  power  scroll  set  softraw  softrepeat  subsystem  uevent

[markus@X1_Carbon]: ~>$ ls /sys/devices/platform/i8042/serio1
bind_mode  description  driver  drvctl  firmware_id  id  input  modalias  power  protocol  rate  resetafter  resolution  resync_time  serio2  subsystem  uevent

[markus@X1_Carbon]: ~>$ ls /sys/devices/platform/i8042/serio1/serio2/
bind_mode    draghys     driver  ext_dev      id       input  mindrag   power            protocol  reach       resolution   sensitivity  speed      thresh  upthresh
description  drift_time  drvctl  firmware_id  inertia  jenks  modalias  press_to_select  rate      resetafter  resync_time  skipback     subsystem  uevent  ztime

Xinput however lists lots of settings. Shouldn't I be able to slow down the speed somehow? Edit: However Accel Speed is 0.000000 ?? How does that add up?

[markus@X1_Carbon]: ~>$ xinput list-props 14                     
Device 'TPPS/2 IBM TrackPoint':
        Device Enabled (141):   1
        Coordinate Transformation Matrix (143): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        libinput Natural Scrolling Enabled (279):       0
        libinput Natural Scrolling Enabled Default (280):       0
        libinput Left Handed Enabled (281):     0
        libinput Left Handed Enabled Default (282):     0
        libinput Accel Speed (283):     0.000000
        libinput Accel Speed Default (284):     0.000000
        libinput Accel Profiles Available (285):        1, 1
        libinput Accel Profile Enabled (286):   1, 0
        libinput Accel Profile Enabled Default (287):   1, 0
        libinput Scroll Methods Available (288):        0, 0, 1
        libinput Scroll Method Enabled (289):   0, 0, 1
        libinput Scroll Method Enabled Default (290):   0, 0, 1
        libinput Button Scrolling Button (291): 2
        libinput Button Scrolling Button Default (292): 2
        libinput Middle Emulation Enabled (293):        0
        libinput Middle Emulation Enabled Default (294):        0
        libinput Send Events Modes Available (264):     1, 0
        libinput Send Events Mode Enabled (265):        0, 0
        libinput Send Events Mode Enabled Default (266):        0, 0
        Device Node (267):      "/dev/input/event18"
        Device Product ID (268):        2, 10
        libinput Drag Lock Buttons (295):       <no items>
        libinput Horizontal Scroll Enabled (296):       1
        Evdev Wheel Emulation Button (659):     1
[markus@X1_Carbon]: ~>$

I also read about libinput reworked acceleration for trackpoints... I guess this has something to do with this https://www.phoronix.com/scan.php?page= … ut-1.9-pre

Last edited by markus21 (2017-11-14 16:44:55)

markus21 · 2017-11-03 12:38:02

Some more information on libinput devices:

[markus@X1_Carbon]: ~>$ sudo libinput list-devices
[sudo] Passwort für markus: 

[......]

Device:           SynPS/2 Synaptics TouchPad
Kernel:           /dev/input/event17
Group:            8
Seat:             seat0, default
Size:             100x56mm
Capabilities:     pointer 
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   none
Rotation:         n/a

Device:           TPPS/2 IBM TrackPoint
Kernel:           /dev/input/event18
Group:            9
Seat:             seat0, default
Capabilities:     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

[...]

Last edited by markus21 (2017-11-03 12:41:23)

tomxtobin · 2017-11-03 14:58:08

Same here. Those libinput 1.9 changes made my trackpoint unusable.

I tried playing with the various options as detailed in /usr/lib/udev/hwdb.d/70-pointingstick.hwdb for sensitivity (POINTINGSTICK_SENSITIVITY) and acceleration factor (POINTINGSTICK_CONST_ACCEL), but I had no luck in getting the old behavior back. Not too surprising, since those settings didn't change between 1.8 and 1.9 (in my case, sensitivity 200, accel 1.0).

I ended up downgrading to libinput 1.8.3. I'm going to be annoyed if I end up having to maintain my own patched libinput — but by now, I should be used to upstream projects constantly removing or breaking things I depend on.

progandy · 2017-11-03 16:20:45

These are probably the relevant commits:
https://github.com/wayland-project/libi … 96f80f57a8
https://github.com/wayland-project/libi … 7a3ef29a61
https://github.com/wayland-project/libi … 7bdd82f2da

It seems you now have LIBINPUT_ATTR_TRACKPOINT_RANGE (0-100, default 20) or alternatively POINTINGSTICK_SENSITIVITY (0-255, default 128)
They relate as RANGE = 20*SENSITIVITY/128
The other settings have been removed, the trackpoint doesn't have POINTINGSTICK_CONST_ACCEL anymore.

Last edited by progandy (2017-11-04 23:03:33)

Hydraulix · 2017-11-04 17:18:42

What's the new way of setting the speed? Before I was doing a:

xset r rate 200 30

markus21 · 2017-11-04 19:04:07

Hydraulix wrote:

What's the new way of setting the speed? Before I was doing a:
xset r rate 200 30

Would really like to know that, too!

justasug · 2017-11-04 22:29:02

I noticed the increased pointer speed too and it was a bit annoying.

You can change the acceleration speed to -1 to make it slower. Use "xinput set-prop" to find a good value and then perhaps add it to an Xorg configuration file to set it permanently (that's what I did).
Changing just the acceleration speed didn't quite cut it for my taste. I also changed the acceleration profile to "flat". You can use "xinput" again to switch to the "flat" one. I added it to my Xorg configuration file. The only downside was that I just copy/pasted the option name, so it feels bad because I have no idea how this works or why (can't find documentation on the exact option names).

Here's what I have in the configuration file:

Section "InputClass"
    Identifier "Trackpoint"
    MatchProduct "TPPS/2 IBM TrackPoint"
    Driver "libinput"
    Option "Accel Speed" "1"
    Option "Accel Profile" "flat"
EndSection

Last edited by justasug (2017-11-04 22:30:05)

cfr · 2017-11-05 02:20:44

justasug wrote:

Here's what I have in the configuration file:

Section "InputClass"
    Identifier "Trackpoint"
    MatchProduct "TPPS/2 IBM TrackPoint"
    Driver "libinput"
    Option "Accel Speed" "1"
    Option "Accel Profile" "flat"
EndSection

Doesn't that maximise the acceleration? So all the work is being done by the profile change?

justasug · 2017-11-05 07:46:38

cfr wrote:

Doesn't that maximise the acceleration? So all the work is being done by the profile change?

True, setting "Accel Speed" to 1 maximizes it. The key thing seems to be using a flat acceleration profile. The combination of the 1 acceleration speed and a "flat" profile comes close to what I had before the update. If it's still too fast for you, try using 0.5 with a flat profile.

Last edited by justasug (2017-11-05 07:48:54)

mohlerm · 2017-11-05 15:35:17

Had the same issue since the update, thanks justasug, using your settings fixed the speed for me.

restl3ss · 2017-11-08 01:44:32

I've had an age-old problem return from the dark ever since upgrading libinput. Basically on my Asus laptop my touchpad is now being identified as a Logitech PS/2 wheel mouse and as a result i've lost all my touchpad gestures and the mouse moves when trying to click around the button areas. It's super annoying. I'm going to try downgrading to 1.8 and see if it fixes the issue

duo8 · 2017-11-08 05:58:33

It's unusable for me too.
I'm on wayland however, and I already have a udev rule to set pointer speed and sensitivity. Is there no way to revert to the old behavior?
Or is there at least some kind of instruction to adapt settings to the new behavior?

markus21 · 2017-11-08 15:39:33

I tried the recommended xorg settings, but even with Accel Speed 0.5 it's not what it's been like before.
By now I just can't remember how it felt, but it felt just way more comfortable. I always liked to use the trackpoint over the touchpad. Now it's just the other way around.

I don't have time right know to try out all combinations of settings possible. So I just leave it how it is for the moment.

IMHO libinput team should make it optional to use the old behaviour since there are several ppl demanding them.

axs · 2017-11-08 17:28:58

Had similar issue several months ago on a Dell laptop, solved it a bit differently:

xinput list # find id of your device
xinput list-props $id # find coordinate transformation matrix
xinput set-prop $id $prop 2 0 0 0 2 0 0 0 10 # tweak the numbers

Ratios matter. Try diag(1 1 10), diag(1 1 20) and so. This may be easier to do than re-configuring udev or editing xorg.conf.
I couldn't make it works as well as it did before that change, but at least it's acceptable now.

justasug · 2017-11-09 14:30:45

markus21 wrote:

I tried the recommended xorg settings, but even with Accel Speed 0.5 it's not what it's been like before.
By now I just can't remember how it felt, but it felt just way more comfortable. I always liked to use the trackpoint over the touchpad. Now it's just the other way around.
I don't have time right know to try out all combinations of settings possible. So I just leave it how it is for the moment.
IMHO libinput team should make it optional to use the old behaviour since there are several ppl demanding them.

Did you switch to the flat profile? I am on 0.7 acceleration with the flat profile and it feels like the old one again.

markus21 · 2017-11-10 11:17:14

justasug wrote:

Here's what I have in the configuration file:

Section "InputClass"
    Identifier "Trackpoint"
    MatchProduct "TPPS/2 IBM TrackPoint"
    Driver "libinput"
    Option "Accel Speed" "1"
    Option "Accel Profile" "flat"
EndSection

Did exactly what justasug suggested. I created a seperate .conf file in /etx/X11/xorg.conf.d/ named 11-trackpoint.conf. Then I changed "Accel Speed" to "0.5". But I still cant feel any noticable decceleration.

Edit: Right now I'm back to libinput 1.8 and the trackpoint is way slower than with libinput 1.9.

Last edited by markus21 (2017-11-10 11:18:18)

progandy · 2017-11-10 11:37:13

markus21 wrote:

justasug wrote:
Here's what I have in the configuration file:
Section "InputClass"
    Identifier "Trackpoint"
    MatchProduct "TPPS/2 IBM TrackPoint"
    Driver "libinput"
    Option "Accel Speed" "1"
    Option "Accel Profile" "flat"
EndSection
Did exactly what justasug suggested. I created a seperate .conf file in /etx/X11/xorg.conf.d/ named 11-trackpoint.conf. Then I changed "Accel Speed" to "0.5". But I still cant feel any noticable decceleration.

As far as I know, for the new trackpoint code Accel Speed = 0 is the default speed, -1 is the slowest setting and +1 is the fastest. 0.5 should be a bit faster than default.

markus21 · 2017-11-10 11:51:56

Did exactly what justasug suggested. I created a seperate .conf file in /etx/X11/xorg.conf.d/ named 11-trackpoint.conf. Then I changed "Accel Speed" to "0.5". But I still cant feel any noticable decceleration.

After pacman -Syu today, i was back to libinput 1.9 and tried the config again, this time it is OK for me – even with accel speed 1. It's much more controllable now. I don't know why. Logical explanation would be: I mixed something up with the config file and the accel profile was not set to "flat".

cfr · 2017-11-10 23:21:19

progandy wrote:

As far as I know, for the new trackpoint code Accel Speed = 0 is the default speed, -1 is the slowest setting and +1 is the fastest. 0.5 should be a bit faster than default.

Setting speed to 1 and the profile to flat is far slower than whatever the default is - at least on my hardware.

I don't really find the trackpoint usable, but that's probably me as I didn't really find it usable on my old laptop either. (I find it almost impossible to move in a smooth curve - straight lines are fine, but turning corners is horrible.)

dreivier · 2017-11-11 11:26:17

Sensitivity is up so much I can barely use my Apple Magic Touchpad (the external BT one). I have to put my fingers flat on the touchpad to get maximum surface between my fingers and touchpad. Then it still randomly "clicks" and it's almost unusable. Would like to know how and where to fix this. I'm on GNOME/Wayland.

cfr · 2017-11-11 20:28:37

dreivier wrote:

Sensitivity is up so much I can barely use my Apple Magic Touchpad (the external BT one). I have to put my fingers flat on the touchpad to get maximum surface between my fingers and touchpad. Then it still randomly "clicks" and it's almost unusable. Would like to know how and where to fix this. I'm on GNOME/Wayland.

I suggest finding a different thread for this problem. Trackpoints are not touchpads! If there is not an existing thread, then start a new one and provide the requisite details. Nobody here has mentioned any change in touchpad behaviour, so yours may be some other kind of configuration issue or hardware quirk.

Arch Linux

#1 2017-11-03 12:27:29

[solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#2 2017-11-03 12:38:02

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#3 2017-11-03 14:58:08

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#4 2017-11-03 16:20:45

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#5 2017-11-04 17:18:42

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#6 2017-11-04 19:04:07

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#7 2017-11-04 22:29:02

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#8 2017-11-05 02:20:44

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#9 2017-11-05 07:46:38

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#10 2017-11-05 15:35:17

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#11 2017-11-08 01:44:32

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#12 2017-11-08 05:58:33

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#13 2017-11-08 15:39:33

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#14 2017-11-08 17:28:58

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#15 2017-11-09 14:30:45

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#16 2017-11-10 11:17:14

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#17 2017-11-10 11:37:13

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#18 2017-11-10 11:51:56

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#19 2017-11-10 23:21:19

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#20 2017-11-11 11:26:17

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

#21 2017-11-11 20:28:37

Re: [solved]Trackpoint behaviour changed after upgrade to libinput 1.9

Board footer