unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: X protocol error
Date: Wed, 17 Aug 2022 15:08:03 +0100	[thread overview]
Message-ID: <87sflvt130.fsf@yandex.com> (raw)
In-Reply-To: <87mtc3oy8d.fsf@yahoo.com> (Po Lu's message of "Wed, 17 Aug 2022 20:23:14 +0800")

Dear Po,

Thanks for your reply. I have narrowed the problem to the configure option
"./configure --with-x-toolkit=lucid <RET>". If I run only "./configure
<RET>", effectively using the gtk3 default setting then emacs builds
successfully.

>>>>> Po Lu <luangruo@yahoo.com> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> On a fresh git clone of emacs and after a seemingly successful
    >> make bootstrap I get the message
    >> 
    >> X protocol error: XI_BadDevice (invalid Device parameter) on
    >> protocol request 131 Serial no: 54
    >> 
    >> when I attempt to launch emacs. I have no idea what the message
    >> means.
    >> 
    >> Best wishes,

    > Please run Emacs under a debugger like this:

    >   (gdb) run -q -xrm "Emacs.synchronous: true"

    > and show the resulting backtrace once the breakpoint on the X
    > error handler is hit.

In an xterm, in my directory ~/git/emacs/src, if I launch gdb and then
enter your command. I get the following:

--8<---------------cut here---------------start------------->8---
gdb$ run -q -xrm "Emacs.synchronous: true"
Starting program:  -q -xrm "Emacs.synchronous: true"
No executable file specified.
Use the "file" or "exec-file" command.
--8<---------------cut here---------------end--------------->8---

I am obviously doing something stupid. I have not used gbd before so you
will have to talk me through the method in some detail. For instance,
must have compiled (made?) emacs using some debugger option? Sorry to
be dim.

Best wishes,




  reply	other threads:[~2022-08-17 14:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <courier.0000000062FCF396.0000215F@stw1.rcdrun.com>
     [not found] ` <Yvz700+TkiqWV/iw@protected.localdomain>
     [not found]   ` <87wnb76icx.fsf@gmail.com>
2022-08-17 10:16     ` X protocol error Colin Baxter
2022-08-17 12:23       ` Po Lu
2022-08-17 14:08         ` Colin Baxter [this message]
2022-08-17 14:31           ` Robert Pluim
2022-08-17 14:55             ` Robert Pluim
2022-08-17 15:29               ` Colin Baxter
     [not found]               ` <Yv0JK7ZKnIlS80NB@protected.localdomain>
2022-08-17 15:34                 ` bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131, " 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-18  2:30               ` X protocol error Po Lu
2022-08-18  6:01                 ` Colin Baxter

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=87sflvt130.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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).