Linux Input/HID development
 help / color / mirror / Atom feed
From: "Benjamin Tissoires" <benjamin.tissoires@gmail.com>
To: "Steven Haigh" <netwiz@crc.id.au>
Cc: "Stéphane Chatty" <chatty@enac.fr>,
	"Peter Hutterer" <peter.hutterer@who-t.net>,
	linux-input@vger.kernel.org
Subject: Re: hid_multitouch - random non-responsive, multitouch, scrolling and zooming
Date: Fri, 10 Oct 2025 15:54:28 +0200	[thread overview]
Message-ID: <ed69f310-8a4d-4023-b1ce-72b78e512177@app.fastmail.com> (raw)
In-Reply-To: <26b03bc2-b824-4948-9803-5a0b5f08e394@crc.id.au>



On Fri, Oct 10, 2025, at 2:21 PM, Steven Haigh wrote:
> On 7/10/25 20:10, Benjamin Tissoires wrote:
>> On Tue, Oct 7, 2025, at 3:42 AM, Steven Haigh wrote:
>>> I ran `libinput record -o recording.yml /dev/event/input6` and have
>>> attached the compressed output. Annoyingly, it seems like the touchpad
>>> is working fine at the moment - so it may confirm the hardware
>>> information, but not a recording of the problem right now.
>> 
>> Yeah, same on one of the Dell laptops I have here. I know it has the bug, but whenever I try to reproduce it it never shows meaning I was never able to pin point the issue :(
>
> So, "good" news is that I managed to grab a recording today when the 
> touchpad started to play up. When using two-fingers to scroll, I ended 
> up zooming etc.

Unfortunately, this is a recording after the kernel processing, so all I can do is check that we have ghost fingers (and even that is trciky because I'm not sure if what we see are the expected events or not).

>
> I tried to make the recording as short as possible, but still include 
> examples of clicking, scrolling etc.
>
> Attached for reference.
>
> As for which way to approach a fix - I'm happy for you to suggest what 
> path we take - a BPF, kernel patch backport, or something else.

Great, thanks!

>
> You tell me which one gives the most value and is likely to help more 
> people in the long run.

Right now the most valuable would be to test the series at
https://lore.kernel.org/linux-input/20251008-fix-sticky-fingers-v1-0-760f1f26fce3@kernel.org/T/#m0fba507cbd43acd36bef28151ecb90b7077606a4

If this work and you want a quick and dirty fix you can then return to the default kernel, and use the BPF from https://gitlab.freedesktop.org/libevdev/udev-hid-bpf/-/merge_requests/204, the latest version should be compatible with your device, just re-download and install it again.

But definitely a tested-by on the kernel patch would be appreciated :)

Cheers,
Benjamin

>
> -- 
> Steven Haigh
>
> 📧 netwiz@crc.id.au
> 💻 https://crc.id.au
> Attachments:
> * recording.yml.xz

  reply	other threads:[~2025-10-10 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2a878c8a-0289-4378-9c32-6eaf57e7dbfc@crc.id.au>
     [not found] ` <d058871a-a2c6-4197-a77c-08edb0ce70b4@app.fastmail.com>
2025-10-07  1:42   ` hid_multitouch - random non-responsive, multitouch, scrolling and zooming Steven Haigh
2025-10-07  9:10     ` Benjamin Tissoires
2025-10-10 12:21       ` Steven Haigh
2025-10-10 13:54         ` Benjamin Tissoires [this message]
2025-10-10 23:30           ` Steven Haigh
2025-11-14  4:04           ` Steven Haigh
2025-11-30  5:56             ` Steven Haigh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed69f310-8a4d-4023-b1ce-72b78e512177@app.fastmail.com \
    --to=benjamin.tissoires@gmail.com \
    --cc=chatty@enac.fr \
    --cc=linux-input@vger.kernel.org \
    --cc=netwiz@crc.id.au \
    --cc=peter.hutterer@who-t.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox