From ArchWiki

Middle-button scrolling with libinput

The article mentions that "When using xf86-input-libinput, middle-button scrolling is enabled by default". That may be so, but not when using a PS/2-to-USB adapter. This way middle-button scrolling does not work. It used to work with evdev. If anybody knows where to set the needed properties for libinput, please amend the article.

--Tskevy (talk) 13:17, 16 March 2017 (UTC)

And it also doesn't work, if using a Thinkpad Trackpoint Keyboard II via Bluetooth. If I use it with the USB adapter, scrolling works out of the box.

--Boesi (talk) 20:24, 18 July 2021 (UTC)

I was able to get the Thinkpad TrackPoint keyboard II (bluetooth) working w/ the udev rule below:

ACTION=="add|change", SUBSYSTEM=="input", ATTRS{name}=="TrackPoint Keyboard II Mouse", ENV{ID_INPUT_POINTINGSTICK}="1"

Niq000 (talk) 16:34, 22 September 2021 (UTC)

The following xorg config snippet works for me using libinput:

Section "InputClass"
  Identifier  "Trackpoint Wheel Emulation"
  MatchDriver "libinput"
  MatchIsPointer "on"
  MatchProduct       "TPPS/2 IBM TrackPoint"
  #MatchProduct        "Teensyduino Serial+Keyboard+Mouse+Joystick"
  MatchDevicePath     "/dev/input/event*"
  Option              "Scroll Method" "button"

Phragment (talk) 01:41, 5 June 2022 (UTC)

udev hwdb entry out-of-date

As yurb (Yuriy Bulka?) has noticed, this seems to be removed: [1].

I have updated the section, but will appreciate if someone reviewed it. Thanks. --Setthemfree (talk) 15:29, 13 June 2018 (UTC)

HP pointing stick sensitivity with libinput - probably applies to other vendors too

Problem: I was unable to adjust sensitivity on a HP pointing stick (listed as "PS/2 Generic Mouse" by xinput) using any of the described methods. There's no "sensitivity" or "deceleration" or similar properties when runing "xinput list-props" and fiddling with the other properties doesn't affect sensitivity.

Solution: One can finely adjust speed using the "Coordinate Transformation Matrix", by changing (only) the first two entries of the main diagonal - that is the first two 1's in the default configuration, to something higher.

In fact, it's possible to make other changes such as direction, etc, (i.e. if one wish to invert an axis or rotate, for whatever reason) or to make one axis more sensitive. Some details regarding how the matrix is applied are listed in the driver documentation here:

I did a quick search and there's no mention of this on the libinput article either. On the one hand maybe it's worth adding in somewhere because it seems rather useful. On the other, I'm not sure if it's the feature is supposed to be used this way since I've only seen it mentioned in regards to touchscreen calibration, so I'm a little reluctant.

Kolo (talk) 02:04, 25 March 2020 (UTC)