[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap paramete
From: |
Eli Zaretskii |
Subject: |
bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55 |
Date: |
Thu, 03 Aug 2017 19:25:24 +0300 |
> Date: Thu, 03 Aug 2017 11:04:00 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 27816@debbugs.gnu.org
>
> With a build from 9.11.2014 I get the same behavior but with the
> meanwhile well-known message:
>
> X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55
>
> In addition, the Emacs process consumes all CPU power it can get.
>
>
> With current master the client frame is shown for a short moment and
> then disappears. The Emacs process does not stall.
Could any of this be related to the change whereby we no longer wait
for the frame to become visible?
> In all cases, the problem occurs reliably - on the average about every
> fifth call of emacsclient.
If you run Emacs in X synchronized mode and put a breakpoint on
x_error_quitter, can you see why the problem happens? Which picmap
parameter is invalid?
> Lucid without toolkit scrollbars doesn't
> build here any more, so far no idea why [does anyone grok ...
>
> In file included from ./string.h:49:0,
> from ../../lib/explicit_bzero.c:28:
> ./stddef.h:93:3: error: conflicting types for ‘max_align_t’
> In file included from ./stddef.h:55:0,
> from ./string.h:49,
> from ../../lib/explicit_bzero.c:28:
> /usr/lib/gcc/x86_64-linux-gnu/4.7/include/stddef.h:426:3: note: previous
> declaration of ‘max_align_t’ was here
> make[1]: *** [explicit_bzero.o] Fehler 1
> make[1]: *** Warte auf noch nicht beendete Prozesse...
> In file included from ./unistd.h:56:0,
> from ../../lib/fcntl.c:28:
> ./stddef.h:93:3: error: conflicting types for ‘max_align_t’
> In file included from ./stddef.h:55:0,
> from ./unistd.h:56,
> from ../../lib/fcntl.c:28:
> /usr/lib/gcc/x86_64-linux-gnu/4.7/include/stddef.h:426:3: note: previous
> declaration of ‘max_align_t’ was here
Sounds like some Gnulib-related issue. Perhaps Paul could help figure
this out.
> BTW, I never use emacsclient and have no idea how to use it. Is there a
> way to stop the server from the starting emacs?
I don't understand the question. When Emacs starts, the server is not
started automatically, so I'm unsure what is it that you want to do.
Please tell me what I missed.
Thanks.
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Jean Louis, 2017/08/02
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Eli Zaretskii, 2017/08/02
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Jean Louis, 2017/08/02
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, martin rudalics, 2017/08/03
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55,
Eli Zaretskii <=
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Glenn Morris, 2017/08/03
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, martin rudalics, 2017/08/03
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Eli Zaretskii, 2017/08/03
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, martin rudalics, 2017/08/04
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Eli Zaretskii, 2017/08/04
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, martin rudalics, 2017/08/04
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Eli Zaretskii, 2017/08/04
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, martin rudalics, 2017/08/05
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, Eli Zaretskii, 2017/08/05
- bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55, martin rudalics, 2017/08/06