linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Ippolito <andrea.ippo@gmail.com>
To: dmitry.torokhov@gmail.com, alex.hung@canonical.com
Cc: linux-i2c@vger.kernel.org, linux-input@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Subject: Re: Touchpad stickiness on Dell Inspiron/XPS
Date: Fri, 27 Aug 2021 08:57:10 +0200	[thread overview]
Message-ID: <CAGhUXvDNj2v3O==+wWWKPYVzej8Vq+WNiBtPwmYxSQ2dTuLb9Q@mail.gmail.com> (raw)
In-Reply-To: <CAGhUXvBw4rzCQrqttyyS=Psxmhppk79c6fDoxPbV91jE7fO_9A@mail.gmail.com>

(resending as plain text)

Hello everyone,

I hope I find you well.

I am writing this to report a touchpad issue faced by me and several
other DELL users across several different distros (HW defect has been
ruled out by people unable to reproduce on Windows).

First thing that came to mind was to report this to the libinput
project, which I did here:

https://gitlab.freedesktop.org/libinput/libinput/-/issues/618

A similar report by another user followed shortly after:

https://gitlab.freedesktop.org/libinput/libinput/-/issues/636 (will be
closed as dupe eventually, so please keep #618 as reference)

Issue has been also reported by yet another user on reddit:

https://www.reddit.com/r/linuxhardware/comments/ofbzg3/dell_xps_15_9510_experience/h5ddy07/
and https://www.reddit.com/r/linuxhardware/comments/ofbzg3/dell_xps_15_9510_experience/h5zjwc8/?utm_source=reddit&utm_medium=web2x&context=3

And finally, I have reported it on the DELL user forums (no help
whatsoever from DELL):

https://www.dell.com/community/Inspiron/Tiger-Lake-DELL-Inspiron-Touchpad-Cursor-temporarily-drops/m-p/8021753#M126292

The investigation on the libinput side appears to be complete, as
maintainers didn't spot anything weird there (also, the issue is also
reproducible with the synaptics lib, suggesting that this might be
lower level).

Robert Martin suggested to raise this to you now, as per comment:

https://gitlab.freedesktop.org/libinput/libinput/-/issues/618#note_1042277

I'm kind of new to Linux mailing lists and bug reporting, so please
forgive me if I'm violating some rules or etiquette, I'd be glad to
rectify if that's the case.

I also don't know what is the best way to keep the conversation going,
e.g. if there's an issue tracker or instead mailing lists are the
preferred choice.

You should find some interesting data in the above mentioned reports
already, if not, please don't hesitate to let me know or chime in on
libinput issue #618 directly.

Thanks a lot in advance.

Kind regards,
Andrea IPPOLITO

       reply	other threads:[~2021-08-27  6:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGhUXvBw4rzCQrqttyyS=Psxmhppk79c6fDoxPbV91jE7fO_9A@mail.gmail.com>
2021-08-27  6:57 ` Andrea Ippolito [this message]
2021-09-23  8:47   ` Touchpad stickiness on Dell Inspiron/XPS Andrea Ippolito
2021-09-23  9:00     ` Hans de Goede
2021-09-23  9:06       ` Andrea Ippolito
2022-01-06 13:14       ` Wolfram Sang
2022-01-11 10:34         ` Touchpad stickiness on AMD laptops (was Dell Inspiron/XPS) Hans de Goede
2022-01-11 11:13           ` Benjamin Tissoires
2022-01-11 23:15             ` Limonciello, Mario
2022-01-12  8:33               ` Wolfram Sang
2022-01-12 12:21                 ` Miroslav Bendík
2022-01-12 22:54                   ` Limonciello, Mario
2022-01-15  9:39                     ` Miroslav Bendík
2022-01-15 13:46                       ` Limonciello, Mario
2022-01-15 18:10                         ` Miroslav Bendík
2022-01-17  8:39                         ` Miroslav Bendík
2022-01-17  9:08                           ` Hans de Goede
2022-01-23 17:25                             ` Miroslav Bendík
2022-01-12 12:31                 ` Hans de Goede
2022-01-30 13:14               ` Miroslav Bendík
2022-02-06 18:13               ` Miroslav Bendík

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='CAGhUXvDNj2v3O==+wWWKPYVzej8Vq+WNiBtPwmYxSQ2dTuLb9Q@mail.gmail.com' \
    --to=andrea.ippo@gmail.com \
    --cc=alex.hung@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).