From: anddam <anddam@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libinput: update to 1.19.1
Date: Tue, 12 Oct 2021 12:22:51 +0200 [thread overview]
Message-ID: <20211012102251.tBbSBR93t-CdiN9IrWigqgA1J_cGcvBkMsquEfFqw9w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33489@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
New comment by anddam on void-packages repository
https://github.com/void-linux/void-packages/pull/33489#issuecomment-940840483
Comment:
> I have been using this version of libinput for a while, but it needs to be tested by as many people as possible.
> cc @anddam - you had some issues with 1.18 if I remember correctly, could you test if this PR fixes it for you?
I had issues but rather than reporting upstream I cowardly reverted the package and lived happily (so far).
I will test this update and report.
**update:**
No, 1.19 does not fix my issue.
My issue is that my Synaptic SYNA3602 touchpad does not send button 2 and 3 events anymore once libinput is updated to 1.18 or more.
It does correctly send button 4, 5, 6 and 7 (that is horizontal and vertical finger scroll) and is able to emit button 3 if multitouch option is enabled, but pressing middle or right physical buttons will result in a button 1 event being emitted.
next prev parent reply other threads:[~2021-10-12 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 19:46 [PR PATCH] " vilhelmbergsoe
2021-10-11 21:08 ` paper42
2021-10-12 9:37 ` anddam
2021-10-12 10:22 ` anddam
2021-10-12 10:22 ` anddam [this message]
2021-10-15 23:00 ` [PR PATCH] [Merged]: " paper42
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=20211012102251.tBbSBR93t-CdiN9IrWigqgA1J_cGcvBkMsquEfFqw9w@z \
--to=anddam@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).