Very user friendly. [LWN.net]

Very user friendly.

Posted Jun 11, 2025 12:45 UTC (Wed) by zdzichu (subscriber, #17118)
In reply to: Very user friendly. by LtWorf
Parent article: Ubuntu 25.10 to drop support for GNOME on Xorg

I can't comprehend what's going on with libinput. From my understanding of the ticket:
– it cares about pressure user's finger exerts on touchpad
– based on pressure, it decides if user used thumb or other finger
– if it decides it was a thumb, then libinput behaves differently than if it was other finger.

I may be wrong, but above sound like very hacky and terrible heuristics.

(FTR, I had many thinpads, currently using t480s and T15 AMD gen2, and the touchpads work fine, although trackpoint is the primary pointing device in them)

Very user friendly.

Posted Jun 13, 2025 13:33 UTC (Fri) by mgedmin (guest, #34497) [Link] (3 responses)

AFAIU from bug comments there what's happening there is that libinput implements gestures (such as pinching), and so it waits a bit more (4 mm of motion in one finger) before starting to scroll, while the Xorg synaptics drive doesn't support gestures and can start scrolling immediately. And then the suggested workaround to disable gesture support doesn't work for unclear reasons.

Very user friendly.

Posted Jun 13, 2025 16:10 UTC (Fri) by LtWorf (subscriber, #124958) [Link] (2 responses)

That's the hypothesis. But I don't think that's it. It takes centimeters to trigger it.

Very user friendly.

Posted Jun 13, 2025 17:17 UTC (Fri) by LtWorf (subscriber, #124958) [Link] (1 responses)

So in the end the issue is closed but 2 finger scrolling does not work. Do you see any willingness to fix it?

Very user friendly.

Posted Jun 13, 2025 23:06 UTC (Fri) by whot (subscriber, #50317) [Link]

> So in the end the issue is closed but 2 finger scrolling does not work. Do you see any willingness to fix it?

The first bugbot comment explicitly states: "we close it, you re-open it when whatever above has been addressed and
then we know we need to look at it again." (and why we use this approach).

So if it's still an issue please re-open and supply any useful log files because writing a statement like "It takes centimeters to trigger it." deep inside LWN comments instead of the gitlab report is not usually going to help getting things fixed. You didn't mention this when I explained the 4mm threshold.

Reading through this again, the answer of "Is there's a chance that you're seeing the erratic behaviour because the second finger may rest in the button area? If you change to clickfinger (--set-click-method=clickfinger in debug-events) does this fix the issue?" was met with a statement about libinput having the wrong default for buttons for you. But that question is still pending.

But, from a personal POV: complaining multiple times in other forums about a project instead of providing the info in the issue trackers is not going to make the maintainers more eager to help. The time I spent writing this could've been spent triaging or fixing some other issue...