Hello everyone, first bug I file, just wanted to say thanks for all your work!! The bug: When setting option ClickMethod to "buttonarea", a right click will not be registered when I have another finger placed on the left button area. That means, the first finger is lying on the left area and I just click on the right area with another finger. Might be the same the other way round, finger lying on the right area and a click on the left. When clicking on a multi-touch enabled touchpad, the click should always be registered. But in this case it will either be a left-click or none at all. It should be a right-click! The click, when happening on a multi-touch-pad, should trigger the correct event depending on where the clicking finger is positioned. For me that would feel natural. I don't know if it is possible to detect which finger is the clicking one - if not, the clicking finger is probably the last one placed on the touchpad. This might also be questionable, so having an option to customize this is probably be nice-to-have (IMHO). I was working on a Fujitsu Lifebook S904 with Ubuntu 15.04 (now upgraded to 15.10, still not working). Libinput came from here and is up-to-date: http://packages.ubuntu.com/de/wily/xserver-xorg-input-libinput Thank you again!
tbh, this isn't something fixable. we do (in most cases) know the positions of the finger but we also use the bottom area for middle button emulation, so if you have two fingers down, one in each area you get a middle click instead. it is also really difficult to guess which button event to send when you have two fingers down and one moved. The touchpad only gives us the location data of each finger and a click event, it doesn't tell us which finger caused the click event. we tend to bias towards the left button here because it's a much more common interaction, especially moving the cursor towards the bottom right and then clicking with a finger should usually cause a left button event. so yeah, not something we can fix unfortunately, mainly because we cannot identify the "clicking finger". this bugzilla doesn't have a CANTFIX resolution, so I'll have to close it as WONTFIX
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.