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

[Eli Zaretskii]

> Date: Sat, 05 Aug 2017 14:46:12 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: bugs@gnu.support, 27816@debbugs.gnu.org
> 
> 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.)

Then I guess this should go in etc/PROBLEMS.