Did you get a new laptop or did you actually swap the clickpad for a new one with separate buttons? I was thinking about buying a replacement part of the x250 and try it on my x240. But my laptop is now also the machine I use for work so I can't take risk like that without knowing that it's going to work.
]]>Yesterday, I found out the best package for you. It is xf86-input-libinput.
https://archive.fosdem.org/2015/schedul … t_xorg.pdf
I think it should work with your touchpads.
Please try this package.
I'm currently setting up my laptop again and noticed that your package is no longer in the AUR. So I started wondering whether there is maybe a new approach to solving the problem but couldn't find anything. Is there a particular reason why your package disappeared from the AUR? Or does it have to do with the AUR3 to AUR4 migration? Your package is most awesome and saved me big time from Lenovo's Clickpad hell.
]]>You can find my packages in https://www.dropbox.com/sh/5mb3px1j6xiu … BYLGa?dl=0.
Since I am not using that buttonless touchpad, version 2.10.0 is not tested.
But version 2.10.0 is generated by just changing version number in PKGBUILD, so I think it will work.
I have a Gentoo installation on a t520p and a t440p. I was saddened when gettng the t440p after hours of configuration attempts resulted in no scroll with middle click. Is there a way to install & get this working on another distro?
I am trying to create an overlay that emerges x11-drivers/xf86-input-synaptics & x11-drivers/xf86-input-evdev with these patches.
0004-disable-clickpad_guess_clickfingers.patch works for synaptics. I can't get either 0001-implement-trackpoint-wheel-emulation.patch nor 0006-add-synatics-files-into-Makefile.am.patch to work with evdev. Which patches are for which packages so I know that I am applying the patches to the right package?
]]>Side note: This large clickpad is such a regression compared to my T61 small trackpad with physical buttons. I keep doing unwanted moves with my palm (and lost a previous version of this message because of that), an annoyance my mother is complaining about on her macbook. How come the Lenovo people decided to go for such an option?
]]>After tinkering with xinput set-props, I managed to get the thing working
Section "InputClass"
Identifier "Clickpad"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
# Synaptics options come here.
Option "TapButton1" "1"
Option "TapButton2" "3"
Option "TapButton3" "2"
Option "SoftButtonAreas" "4000 0 0 2600 2550 4000 0 2600"
Option "AreaTopEdge" "2600"
Option "AreaBottomEdge" "0"
EndSection
Section "InputClass"
Identifier "TrackPoint"
MatchProduct "TrackPoint"
MatchDriver "evdev"
Option "EmulateWheel" "1"
Option "EmulateWheelButton" "2"
Option "XAxisMapping" "6 7"
EndSection
The issue is I reinstalled synaptics after deleting the config, then installed xf86-input-evdev-trackpoint.conf but seems the config isn't used.
Lenovo Thinkpad E431
arch 64bit, KDE
kcm_synaptics is used as a client
Didn't try tmpfiles as you said it would not work. Why do you use .xprofile now, instead of the udev rule (I mean, what's the advantage of that way) ?
Regards
EDIT: @jck: Could you post your .xprofile config please? I'm struggling with permissions when trying to set the trackpoint settings.
]]>You can use systemd's tmpfiles feature instead of the udev rule. See here:
https://wiki.archlinux.org/index.php/sy … rary_files
BTW, do you install regular synaptics in addition to the evdev-trackpoint package?
EDIT: Tmpfiles.d does not appear to work for this. I'm just calling a shell script from .xprofile for now.
]]>