[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25474: 26.0.50; Buffer content invisible
From: |
Eli Zaretskii |
Subject: |
bug#25474: 26.0.50; Buffer content invisible |
Date: |
Thu, 19 Jan 2017 05:33:58 +0200 |
> From: "Ivor Durham" <ivor.durham@ivor.cc>
> Cc: <25474@debbugs.gnu.org>
> Date: Wed, 18 Jan 2017 13:27:21 -0800
>
> Here is the output from M-X dump-glyph-matrix after invoking emacs -Q:
Thanks. This output means that the Emacs display engine produced the
required display of the initial frame, and therefore the prime suspect
is the interaction with X.
Can you try running in X synchronous mode? Like this:
emacs -Q -xrm "emacs.synchronous: true"
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/18
- bug#25474: 26.0.50; Buffer content invisible, Eli Zaretskii, 2017/01/18
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/18
- bug#25474: 26.0.50; Buffer content invisible, Eli Zaretskii, 2017/01/18
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/18
- bug#25474: 26.0.50; Buffer content invisible, Eli Zaretskii, 2017/01/18
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/18
- bug#25474: 26.0.50; Buffer content invisible,
Eli Zaretskii <=
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/19
- bug#25474: 26.0.50; Buffer content invisible, Eli Zaretskii, 2017/01/19
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/19
- bug#25474: 26.0.50; Buffer content invisible, Eli Zaretskii, 2017/01/19
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/19
- bug#25474: 26.0.50; Buffer content invisible, Eli Zaretskii, 2017/01/20
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/20
- bug#25474: 26.0.50; Buffer content invisible, Daniel Colascione, 2017/01/20
- bug#25474: 26.0.50; Buffer content invisible, Eli Zaretskii, 2017/01/20
- bug#25474: 26.0.50; Buffer content invisible, Ivor Durham, 2017/01/20