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

[martin rudalics]

> etc/DEBUG suggests to evaluate (x-synchronize t).

Gets me

Debugger entered--Lisp error: (error "X windows are not in use or not 
initialized")
  x-synchronize(t)

here.

>> Apparently, the shadow calculations for the Xaw3D scroll bars, when
>> done from a TTY-started server, are sometimes not digested by X11.
>
> Can you try figuring out why is that?

I have no idea how to do that.  Passing no arguments to XtCreateWidget
doesn't help so IIUC the problem is somewhere in between
Xaw3dComputeTopShadowRGB and XQueryColor but maybe someone has a better
explanation.


BTW, this behavior has been reported in bug#5802 where it says:

  When the lucid version, emacs does not crash, but for some reason,
  when I run the emacsclient frame-creating loop that I described
  previously, sometimes the client frame disappears as soon as it
  appears, and I assumed that a crash had occurred. But in this case,
  emacs does not crash, and I only get the problem in a loop like this.
  Simply running "emacsclient -c" manually over and over at the
  command-line never causes a frame to disappear. So, I think I will
  move forward using the lucid version, and you can mark this as a GTK
  problem.

And obviously this is bug#23499 where you stated:

  Error code 4 is BadPixmap, according to my references.  I hope some X
  expert will chime in and tell why this happens.  (I actually don't
  understand why we try to create the scroll bar when the frame is
  iconified.)

martin