From: Robert Pluim <rpluim@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: 57261@debbugs.gnu.org
Subject: bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131
Date: Wed, 17 Aug 2022 16:43:26 +0200 [thread overview]
Message-ID: <87wnb76icx.fsf@gmail.com> (raw)
In-Reply-To: <Yvz700+TkiqWV/iw@protected.localdomain> (Jean Louis's message of "Wed, 17 Aug 2022 17:31:47 +0300")
>>>>> On Wed, 17 Aug 2022 17:31:47 +0300, Jean Louis <bugs@gnu.support> said:
Jean> I could not start X version of Emacs at all.
Jean> I am on latest git version.
Jean> What worked is `emacs -nw --bg-daemon':
Jean> but Emacs is not starting on X now.
Does this help:
diff --git a/src/xterm.c b/src/xterm.c
index a40440e0da..a329ca59d0 100644
--- a/src/xterm.c
+++ b/src/xterm.c
@@ -27654,6 +27654,8 @@ xi_select_hierarchy_events (struct x_display_info *dpyinfo)
memset (m, 0, l);
mask.mask_len = l;
+ mask.deviceid = XIAllDevices;
+
XISetMask (m, XI_PropertyEvent);
XISetMask (m, XI_HierarchyChanged);
XISetMask (m, XI_DeviceChanged);
Robert
--
next prev parent reply other threads:[~2022-08-17 14:43 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 [this message]
[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
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=87wnb76icx.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=57261@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).