Arch Linux

schokomuesli

Member

Registered: 2019-11-16

Posts: 1

Libinput doesn't recognize two-finger scrolling option of touchpad

Hi guys,

since 10-Nov-2019 i encountered a problem. Libinput (xf86-input-libinput driver) doesnt recognize the two-finger scrolling of my touchpad anymore (dont get confused of the device name cotainung 'synaptics', code below shows that im using libinput, order is "two-finger", "edge", "button")

xinput list-props 'PS/2 Synaptics TouchPad'
Device 'PS/2 Synaptics TouchPad':
	Device Enabled (142):	1
	[...]
	libinput Scroll Methods Available (282):	0, 0, 1
	libinput Scroll Method Enabled (283):	0, 0, 1
	libinput Scroll Method Enabled Default (284):	0, 0, 1
	libinput Button Scrolling Button (285):	2
	libinput Button Scrolling Button Default (286):	2
	[...]

Instead it offers me a scrollbutton, that im still searching on my laptop And yes somebody will say when libinput says my touchpad dont offer this method, I dont have it, but befor 10-Nov it worked all fine
Additionally on 10-Nov-2019 i removed synaptics, bc i thought that i dont need it anymore. maybe i was wrong. I thought i was running on libinput long time before that.

[2019-11-10T20:05:07+0100] [PACMAN] Running 'pacman -R xf86-input-synaptics'
[2019-11-10T20:05:26+0100] [ALPM] transaction started
[2019-11-10T20:05:36+0100] [ALPM] removed xf86-input-synaptics (1.9.1-1)
[2019-11-10T20:05:36+0100] [ALPM] transaction completed
[2019-11-10T20:05:36+0100] [ALPM] running '30-systemd-update.hook'...

So then i tried to reinstall synaptics, using the same config, cause i havent deleted that one yet. But it doesnt worked anymore. (i know it wouldnt be that easy)

So before i damage my brain by reading some deeper xorg-stuff, maybe some of you have a hint or tip, maybe had the same problem with synaptics and libinput (i read through a few of them, but none of them helped me anyway).

5.3.11-arch1-1 kernel version

Thanks 4 your help.

(i can serve with some more logs and debugging output if needed)

P.S.: i dont know if this can be reported as a bug due i dont quite know if its a layer-8 problem xD