bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55

[Eli Zaretskii <eliz@gnu.org>]

> Date: Wed, 2 Aug 2017 19:12:30 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: Jean Louis <bugs@gnu.support>, 27816@debbugs.gnu.org
> 
> My configuration of GNU Emacs is following:
> 
> ./configure --prefix=/package/text/emacs-26.0.50 --with-sound=alsa --with-modules --with-x-toolkit=lucid --without-gconf --without-gsettings --without-libsystemd --without-dbus --without-pop --with-mailutils --without-imagemagick --with-x
> 
> I am still getting:
> 
> X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55
> 
> And I have tried starting Emacs daemon in background without my
> ~/.emacs so it is still happening without custom configuration.

Please describe the sequence of actions leading to the problem in more
detail.  Here's what you said about that last time:

> What I do, I read email by using mutt, then I hit r to reply email,
> including your emails, and I can see the notice from emacsclient on
> console, but the graphic frame is dropped, and later I see the bug in
> Emacs.

This is not detailed enough for me to understand what is going on.  I
presume that mutt somehow invokes emacsclient and you then expect
Emacs to allow you to edit the response to an email message before
sending it.  But even if that guess is correct, it doesn't say whether
emacsclient is invoked to open a new frame or reuse an old frame,
whether that frame is a GUI frame or a text-mode frame, and whether
any other Emacs frames existed before the invocation of emacsclient
and were supposed to remain after you finish editing the response.

Btw, does this happen only when emacsclient is invoked from mutt, or
also with other programs?  What if you invoke emacsclient from the
shell prompt -- does the problem happen if you invoke it several times
in a row?

Also, are you sure the version of emacsclient that is invoked belongs
to the version of Emacs which is run in the daemon mode?

And finally, if you start Emacs not in daemon mode and then use mutt
as you normally do with daemon, does the problem persist or does it go
away?

> emacsclient is basically remaining in memory as process, but the frame
> is disappearing.

So Emacs now runs without any frames displayed?

> It is annoying as it makes programs wait on emacs client to come back,
> as it blocks the console, right?

That depends how emacsclient is invoked.  But if you invoke it from
mutt to edit a response, then you must let it block mutt, because mutt
cannot proceed with sending your response until Emacs is done editing
it.

> Do you think that reason for that can be that I use lucid kit?

I very much doubt that.

> Now I cannot understand what happened that it started showing this
> error, it is being shown in each 4th 5th or so attempt to spawn
> emacsclient.

Something has changed on your system, it seems.