From: Michael Welsh Duggan <mwd@md5i.com>
To: 57261@debbugs.gnu.org
Cc: Po Lu <luangruo@yahoo.com>, Robert Pluim <rpluim@gmail.com>,
Jean Louis <bugs@gnu.support>
Subject: bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131
Date: Wed, 17 Aug 2022 13:02:30 -0400 [thread overview]
Message-ID: <87y1vmst09.fsf@md5i.com> (raw)
In-Reply-To: <87wnb76icx.fsf@gmail.com> (Robert Pluim's message of "Wed, 17 Aug 2022 16:43:26 +0200")
Bisected to this commit:
commit b4879603fd8f9c8e82e30c5fbb65fa63d8166ee4 (HEAD, refs/bisect/bad)
Author: Po Lu <luangruo@yahoo.com>
Date: Tue Aug 16 21:11:03 2022 +0800
Fix XInput hierarchy events not being delivered in daemon mode
* src/xfns.c (setup_xi_event_mask): Stop selecting for device
hierarchy events.
* src/xterm.c (xi_select_hierarchy_events, x_term_init): Select
those here instead, on the default root window.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2022-08-17 17:02 UTC|newest]
Thread overview: 9+ 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
[not found] ` <87wnb79nu7.fsf@yandex.com>
[not found] ` <87mtc3oy8d.fsf@yahoo.com>
[not found] ` <87sflvt130.fsf@yandex.com>
[not found] ` <871qtf7xhe.fsf@gmail.com>
2022-08-17 15:26 ` 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
[not found] ` <87k0767ujz.fsf@gmail.com>
2022-08-18 13:17 ` bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131 Lars Ingebrigtsen
2022-08-17 17:02 ` Michael Welsh Duggan [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1vmst09.fsf@md5i.com \
--to=mwd@md5i.com \
--cc=57261@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=luangruo@yahoo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).