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

[Jean Louis <bugs@gnu.support>]

Dear Eli,

Thank you so far. See below my answers.

On Wed, Aug 02, 2017 at 09:51:13PM +0300, Eli Zaretskii wrote:
> > ./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 will try changing the lucid to gtk kit to see if
it is happening again.

> > 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.

That is just one application on how I start
emacsclient, but mutt is not related to it.

Another way of starting emacs is from terminal is
as this:

emacsclient -s tmp/emacs1001/server -c
Waiting for Emacs...

then each few times it works, like 85%, then it
fails.

Emacs is running in background under screen, and
it has (server-start) in .emacs or when I was
testing without ~/.emacs I evaluated
(server-start) in *scratch* buffer.

28078 pts/0    Ssl+   2:02 /usr/bin/emacs --user admin --chdir /home/data1/protected

Then I run the emacsclient in following fashion:

30859 pts/2    S+     0:00 emacsclient -c -s /home/data1/protected/tmp/emacs1001/server /home/data1/protected/tmp/mutt-protected-1001-30834-15325602171702686152

That means my main Emacs is running in console
under screen, it is not just backgrounded
daemon. But I do not think that it is related to
screen.

I have noticed it now, that if one frame is open,
the error is not appearing on the second frame.

It appears only when there is no existing frame,
and new frame instance has to be open.

> guess is correct, it doesn't say whether
> emacsclient is invoked to open a new frame or
> reuse an old frame

The bug is appearing on opening a new instance of
emacsclient frame when there is no other frame
present.

> whether that frame is a GUI frame or a text-mode
> frame

There is no problem with text mode frames. Just
with GUI frame.

> and whether any other Emacs frames existed
> before the invocation of emacsclient and were
> supposed to remain after you finish editing the
> response.

The text emacs is running under screen.

> Btw, does this happen only when emacsclient is
> invoked from mutt, or also with other programs?

It happens if I invoke emacsclient by any means,
when it is opening first frame.

> What if you invoke emacsclient from the shell
> prompt -- does the problem happen if you invoke
> it several times in a row?

Exactly like that, it happens if I invoke it from
terminal.

Also if I invoke it directly on keypress from
Window Manager or through mutt.

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

Yes, very sure. I am running
emacs-repository-version
"cf1da46761675f1886e54765fa213c7bd7d93437"

And emacs is then in /package/text/emacs/ and
emacs client is then linked to the version I am
running:
admin-> ls -l /usr/bin/emacsclient 
lrwxrwxrwx 1 root root 40 Aug  2 18:55 /usr/bin/emacsclient -> ../../package/text/emacs/bin/emacsclient

and because it is in /package/text/emacs/ it
belongs to same version.

> 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?

You mean if I run emacs without daemon? There is no problem at all.
But due to loading times, and configuration, it is not usable.

> > emacsclient is basically remaining in memory as process, but the frame
> > is disappearing.
> 
> So Emacs now runs without any frames displayed?

Emacs runs all the time, as main program under screen, I can access it
through screen. 

The problem is also happening when I do not run it under screen, I can
run it as user.

If there is no GUI frame, and I wish to invoke it by emacsclient, each
few times, the instance failes, GUI frame disappears, but the
emacsclient still runs in memory, until I kill it.

> > 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.

I do not have dsitribution and did not update system in any manner,
neither touched X Window or similar. I have updated security
certificates, just nothing special on the system.

Jean