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

[Jean Louis]

Hello Eli,

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.

I have also tested it on different Window Managers.

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

It is annoying as it makes programs wait on emacs client to come back,
as it blocks the console, right? Because it blocks the console, the
frame disappeared, the emacs client runs in memory but is not coming
back. Then I have to kill $(pgrep emacsclient) to make it work again. 

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

The reason that I use the lucid kit is because there was similar bug
that Emacs daemon was crushing in the GTK kit. Lucid kit is much more
stable for me.

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.

Jean