Since updating to Tumbleweed 20150418 I noticed a weird behaviour in the Synaptics touchpad “tapping”:
often a single tap is read as “secondary button” (or “right click”) while a “two finger tap” is read as a “middle button click” instead of the desired “right click”.
Three-finger tap is not read at all, apparently, instead of the desired “middle-click”.
Formerly I noticed a similar behaviour with Gnome-on-wayland sessions and thought the culprit was wayland, but now I see it on regular Gnome and with wayland disabled on gdm as well.
Anybody else seeing this, or is my touchpad looking for the wastebin?
>
> Since updating to Tumbleweed 20150418 I noticed a weird behaviour in
> the Synaptics touchpad “tapping”:
> often a single tap is read as “secondary button” (or “right click”)
> while a “two finger tap” is read as a “middle button click” instead of
> the desired “right click”.
> Three-finger tap is not read at all, apparently, instead of the
> desired “middle-click”.
> Formerly I noticed a similar behaviour with Gnome-on-wayland sessions
> and thought the culprit was wayland, but now I see it on regular Gnome
> and with wayland disabled on gdm as well.
>
> Anybody else seeing this, or is my touchpad looking for the wastebin?
>
>
several people on the factory mailing-list are seeing touch-pad problems
with that release. I tried to configure mine but got the message that it
wasn’t found. To add insult to injury, the web-page I was directed to
didn’t exist. I haven’t got round to putting in a bug report yet; will
try the latest updates then, if it’s still a problem, I’ll put one in -
if it’s not already there.
–
Graham Davis [Retired Fortran programmer - now a mere computer user]
openSUSE Tumbleweed (64-bit); KDE 4.14.6; Kernel: 3.19.4;
Processor: AMD Phenom II X2 550; Video: nVidia GeForce 210 (using
nouveau driver); Sound: ATI SBx00 Azalia (Intel HDA)
IIRC latest TW switched to using libinput in Xorg by default. That indeed means that there is probably no touchpad as expected by configuration software. Someone posted in thread on factory that disabling libinput “fixed” it by reverting to previous drivers.
There will be fun until all settings applets catch up
Yes, libinput is the culprit. I got a new notebook, a T450s, which has known issues with the touchpad (new piece of hardware). So I installed openSuse 13.2 and all regular updates, which did not help much. The touchpad still was crippled. After this, I did something which is not correct: I added the tumbleweed repo to install the new kernel 4.0, which, two days ago, was not provided there. But tumbleweed suggested to install libinput-udev and libinput10 and xf86-input-libinput, what I accepted without thinking about it.
Until I read this thread I did not remember this step. But now, I deleted those three packages, rebooted and with the new kernel 4.0 (from HEAD) everything works as expected! Well, at least during the last five minutes…
Confirming that.
My system, updated to TW 20150418, had a libinput5 leftover.
I uninstalled it, toghether with libinput-udev and xf86-input-libinput.
Had to keep libinput10 because of a mutter dependency.
Now the touchpad is working again, apparently driven by libevdev, at least for the last 5 minutes
Still crippled on wayland though.
There has been a lot of traffic on different forums recommending to primarily update “xf86-input-synaptics-1.8.2-76.1.x86_64.rpm” and “xf86-input-evdev-2.9.2-54.1.x86_64.rpm” (or higher).
Recent patches have been applied over the last 2 - 3 months to accommodate changes to the latest Lenovo Thinkpad touchpads and trackpad buttons on the T-series and W-series.
Additional mapping for these laptops have been added to the release of kernel 4.0.0x.
