From: Jiri Kosina <jkosina@suse.cz>
To: David Revoy <davidrevoy@protonmail.com>
Cc: "jason.gerecke@wacom.com" <jason.gerecke@wacom.com>,
"jose.exposito89@gmail.com" <jose.exposito89@gmail.com>,
"ilya.ostapyshyn@gmail.com" <ilya.ostapyshyn@gmail.com>,
Nils Fuhler <nils@nilsfuhler.de>,
Ping Cheng <ping.cheng@wacom.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: Requesting your attention and expertise regarding a Tablet/Kernel issue
Date: Wed, 1 Nov 2023 20:37:40 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2311012033290.29220@cbobk.fhfr.pm> (raw)
In-Reply-To: <kRKTNDYigUSblpNgSuZ2H4dX03Of1yD4j_L9GgbyKXcDqZ67yh5HOQfcd7_83U3jZuQzxpKT3L6FXcRkkZIGdl_-PQF14oIB0QmRSfvpc2k=@protonmail.com>
On Wed, 1 Nov 2023, David Revoy wrote:
> Hi Jason Gerecke, José Expósito, Jiri Kosina and Illia Ostapyshyn,
>
> I am emailing to draw your attention and expertise to a problem I had
> earlier this week with my Xp-Pen Artist 24 Pro display tablet under
> Fedora Linux 38 KDE after a kernel update.
>
> The second button on my stylus changed from a right-click (which I could
> customise with xsetwacom or any GUI like kcm-tablet) to a button that
> feels 'hardcoded' and now switches the whole device to an eraser mode.
> This makes my main tool unusable.
>
> I don't have the skills to write a proper kernel bug report, workaround
> or even identify the exact source of the issue. I have written a blog
> post about this with more details here:
> https://www.davidrevoy.com/article995/how-a-kernel-update-broke-my-stylus-need-help
> , contacting you was something suggested by the comments.
>
> Thank you very much if you can help me.
CCing a couple more people involved both in 276e14e6c3 and 87562fcd1342,
and mailinglists.
This is almost certainly the behavior introduced by 276e14e6c3, where
previously the button was mapped to BTN_TOUCH, but now it's mapped to
BTN_TOOL_RUBBER, causing user-visible change in behavior.
--
Jiri Kosina
SUSE Labs
next parent reply other threads:[~2023-11-01 19:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kRKTNDYigUSblpNgSuZ2H4dX03Of1yD4j_L9GgbyKXcDqZ67yh5HOQfcd7_83U3jZuQzxpKT3L6FXcRkkZIGdl_-PQF14oIB0QmRSfvpc2k=@protonmail.com>
2023-11-01 19:37 ` Jiri Kosina [this message]
2023-11-02 0:44 ` Requesting your attention and expertise regarding a Tablet/Kernel issue Bagas Sanjaya
2023-11-02 6:31 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-02 7:51 ` Bagas Sanjaya
2023-11-02 7:44 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-12-01 8:24 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-03 20:05 ` Illia Ostapyshyn
2023-11-04 0:46 ` Bagas Sanjaya
2023-11-06 13:17 ` David Revoy
2023-11-06 16:59 ` Benjamin Tissoires
2023-11-06 20:06 ` Illia Ostapyshyn
2023-11-07 7:59 ` Benjamin Tissoires
2023-11-07 13:40 ` Illia Ostapyshyn
2023-11-08 5:23 ` Eric GOUYER
2023-11-08 9:04 ` Benjamin Tissoires
2023-11-08 9:23 ` José Expósito
2023-11-08 9:34 ` Benjamin Tissoires
2023-11-08 18:21 ` Benjamin Tissoires
2023-11-09 0:32 ` David Revoy
2023-11-09 11:56 ` Benjamin Tissoires
2023-11-09 16:13 ` Benjamin Tissoires
2023-11-09 22:04 ` David Revoy
2023-11-10 10:19 ` Benjamin Tissoires
2023-11-11 8:52 ` Benjamin Tissoires
2023-11-13 22:08 ` David Revoy
2023-11-14 14:35 ` Benjamin Tissoires
2023-11-15 15:14 ` Benjamin Tissoires
2023-11-23 22:12 ` David Revoy
2023-11-24 17:18 ` Benjamin Tissoires
2023-11-29 15:32 ` Benjamin Tissoires
2023-11-30 22:25 ` David Revoy
2023-12-01 15:41 ` Benjamin Tissoires
2023-11-08 19:40 ` Nils Fuhler
2023-11-08 20:34 ` Benjamin Tissoires
2023-11-08 22:31 ` ostapyshyn
2023-11-09 11:46 ` Benjamin Tissoires
2023-11-08 23:18 ` David Revoy
2023-11-09 11:47 ` Benjamin Tissoires
2023-11-11 17:15 ` Thorsten Leemhuis
2023-11-08 22:28 ` David Revoy
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=nycvar.YFH.7.76.2311012033290.29220@cbobk.fhfr.pm \
--to=jkosina@suse.cz \
--cc=benjamin.tissoires@redhat.com \
--cc=davidrevoy@protonmail.com \
--cc=ilya.ostapyshyn@gmail.com \
--cc=jason.gerecke@wacom.com \
--cc=jose.exposito89@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nils@nilsfuhler.de \
--cc=peter.hutterer@who-t.net \
--cc=ping.cheng@wacom.com \
/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).