From: Robert Pluim <rpluim@gmail.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: X protocol error
Date: Wed, 17 Aug 2022 16:31:25 +0200 [thread overview]
Message-ID: <871qtf7xhe.fsf@gmail.com> (raw)
In-Reply-To: <87sflvt130.fsf@yandex.com> (Colin Baxter's message of "Wed, 17 Aug 2022 15:08:03 +0100")
>>>>> On Wed, 17 Aug 2022 15:08:03 +0100, Colin Baxter <m43cap@yandex.com> said:
Colin> Dear Po,
Colin> Thanks for your reply. I have narrowed the problem to the configure option
Colin> "./configure --with-x-toolkit=lucid <RET>". If I run only "./configure
Colin> <RET>", effectively using the gtk3 default setting then emacs builds
Colin> successfully.
Colin> gdb$ run -q -xrm "Emacs.synchronous: true"
Colin> Starting program: -q -xrm "Emacs.synchronous: true"
Colin> No executable file specified.
Colin> Use the "file" or "exec-file" command.
I think Po Lu meant:
$ cd src
$ gdb emacs
gdb$ run -q -xrm "Emacs.synchronous: true"
I can reproduce this with a lucid build (with XI2 enabled):
Thread 1 "emacs" hit Breakpoint 2, x_error_quitter (display=0x555555f79210,
event=0x7fffffffc1c0) at xterm.c:24762
24762 if (event->error_code == BadName)
(gdb) bt
#0 x_error_quitter (display=0x555555f79210, event=0x7fffffffc1c0)
at xterm.c:24762
#1 0x00005555556e5f2c in x_error_handler
(display=0x555555f79210, event=0x7fffffffc1c0) at xterm.c:24743
#2 0x00007ffff7992864 in _XError () at /lib/x86_64-linux-gnu/libX11.so.6
#3 0x00007ffff798f327 in () at /lib/x86_64-linux-gnu/libX11.so.6
#4 0x00007ffff798f3c5 in () at /lib/x86_64-linux-gnu/libX11.so.6
#5 0x00007ffff799062d in _XReply () at /lib/x86_64-linux-gnu/libX11.so.6
#6 0x00007ffff798be2b in XSync () at /lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007ffff798becb in () at /lib/x86_64-linux-gnu/libX11.so.6
#8 0x00007ffff5b8dac1 in XISelectEvents () at /lib/x86_64-linux-gnu/libXi.so.6
#9 0x00005555556ebc0d in xi_select_hierarchy_events (dpyinfo=0x555555f8bce0)
at xterm.c:27661
#10 0x00005555556ecbf1 in x_term_init
(display_name=XIL(0x555555f65944), xrm_option=0x555555f0af88 "Emacs.synchronous: true", resource_name=0x555555f636f0 "emacs") at xterm.c:28299
#11 0x000055555570082e in Fx_open_connection
(display=XIL(0x555555f65944), xrm_string=XIL(0x555555f499b4), must_succeed=XIL(0x30)) at xfns.c:7260
#12 0x00005555557e3b05 in funcall_subr
(subr=0x555555dd7a00 <Sx_open_connection>, numargs=3, args=0x7ffff18a31d0)
at eval.c:3056
#13 0x00005555558331e1 in exec_byte_code
(fun=XIL(0x7ffff1ff945d), args_template=513, nargs=2, args=0x7ffff18a3348)
at bytecode.c:809
#14 0x00005555557e3dbd in fetch_and_exec_byte_code
(fun=XIL(0x7ffff22ec765), args_template=256, nargs=0, args=0x7ffff18a3150)
at eval.c:3101
#15 0x00005555557e4131 in funcall_lambda
(fun=XIL(0x7ffff22ec765), nargs=0, arg_vector=0x7ffff18a3150)
at eval.c:3173
#16 0x00005555557e36a6 in funcall_general
(fun=XIL(0x7ffff22ec765), numargs=0, args=0x7ffff18a3150) at eval.c:2964
#17 0x00005555557e3902 in Ffuncall (nargs=1, args=0x7ffff18a3148)
at eval.c:3014
#18 0x00005555557e2a58 in Fapply (nargs=2, args=0x7ffff18a3148) at eval.c:2638
#19 0x00005555557e3ce9 in funcall_subr
(subr=0x555555de0600 <Sapply>, numargs=2, args=0x7ffff18a3148)
at eval.c:3079
#20 0x00005555558331e1 in exec_byte_code
(fun=XIL(0x7ffff23d5bed), args_template=770, nargs=3, args=0x7ffff18a33c0)
at bytecode.c:809
#21 0x00005555557e3dbd in fetch_and_exec_byte_code
(fun=XIL(0x7ffff22ea715), args_template=0, nargs=0, args=0x7fffffffdb40)
at eval.c:3101
#22 0x00005555557e4131 in funcall_lambda
(fun=XIL(0x7ffff22ea715), nargs=0, arg_vector=0x7fffffffdb40)
at eval.c:3173
#23 0x00005555557e3f4f in apply_lambda
(fun=XIL(0x7ffff22ea715), args=XIL(0), count=...) at eval.c:3123
#24 0x00005555557e2651 in eval_sub (form=XIL(0x7ffff2730653)) at eval.c:2564
#25 0x00005555557e1c39 in Feval (form=XIL(0x7ffff2730653), lexical=XIL(0))
at eval.c:2375
#26 0x0000555555720edc in top_level_2 () at keyboard.c:1141
#27 0x00005555557dfb8a in internal_condition_case
(bfun=0x555555720eb9 <top_level_2>, handlers=XIL(0x90), hfun=0x555555720807 <cmd_error>) at eval.c:1497
#28 0x0000555555720f24 in top_level_1 (ignore=XIL(0)) at keyboard.c:1149
#29 0x00005555557df252 in internal_catch
(tag=XIL(0xf7e0), func=0x555555720ede <top_level_1>, arg=XIL(0))
at eval.c:1220
#30 0x0000555555720dfd in command_loop () at keyboard.c:1109
#31 0x00005555557203b2 in recursive_edit_1 () at keyboard.c:719
#32 0x000055555572055b in Frecursive_edit () at keyboard.c:802
#33 0x000055555571ca50 in main (argc=4, argv=0x7fffffffe0f8) at emacs.c:2517
Lisp Backtrace:
"x-open-connection" (0xf18a31d0)
0xf22ec760 PVEC_COMPILED
"apply" (0xf18a3148)
"window-system-initialization" (0xf18a30b8)
"command-line" (0xf18a3040)
"normal-top-level" (0xffffdb40)
Robert
--
next prev parent reply other threads:[~2022-08-17 14:31 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 [this message]
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 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qtf7xhe.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=m43cap@yandex.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.