From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: luangruo@yahoo.com, Colin Baxter <m43cap@yandex.com>,
57261@debbugs.gnu.org, Jean Louis <bugs@gnu.support>,
emacs-devel@gnu.org
Subject: bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131
Date: Thu, 18 Aug 2022 15:17:22 +0200 [thread overview]
Message-ID: <87wnb57kt9.fsf_-_@gnus.org> (raw)
In-Reply-To: <87k0767ujz.fsf@gmail.com> (Robert Pluim's message of "Wed, 17 Aug 2022 17:34:40 +0200")
Robert Pluim <rpluim@gmail.com> writes:
> It looks like the right thing, but Iʼd like Po Lu to confirm before I
> push (I know very little about XInput2).
Seems like this was pushed, so I'm closing this bug report.
next prev parent reply other threads:[~2022-08-18 13:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 13:56 bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131 Jean Louis
2022-08-17 14:31 ` Jean Louis
2022-08-17 14:43 ` Robert Pluim
2022-08-17 10:16 ` X protocol error Colin Baxter
2022-08-17 12:23 ` Po Lu
2022-08-17 14:08 ` Colin Baxter
2022-08-17 14:31 ` Robert Pluim
2022-08-17 14:55 ` Robert Pluim
2022-08-17 15:29 ` Colin Baxter
2022-08-18 2:30 ` Po Lu
2022-08-18 6:01 ` Colin Baxter
2022-08-17 15:26 ` bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131 Jean Louis
2022-08-17 15:28 ` Jean Louis
2022-08-17 15:34 ` bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131, Re: X protocol error Robert Pluim
2022-08-17 15:34 ` Robert Pluim
2022-08-18 13:17 ` Lars Ingebrigtsen [this message]
2022-08-17 17:02 ` bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131 Michael Welsh Duggan
2022-08-17 17:02 ` Michael Welsh Duggan
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=87wnb57kt9.fsf_-_@gnus.org \
--to=larsi@gnus.org \
--cc=57261@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=m43cap@yandex.com \
--cc=rpluim@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.