GNU bug report logs - #61667
29.0.60; Failure to redisplay

Previous Next

Full log

View this message in rfc822 format

From: Po Lu <luangruo <at> yahoo.com>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 61667 <at> debbugs.gnu.org, Gregory Heytings <gregory <at> heytings.org>, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#61667: 29.0.60; Failure to redisplay
Date: Wed, 01 Mar 2023 20:41:09 +0800

Dmitry Gutov <dgutov <at> yandex.ru> writes:

> Nope, it's for the "no problem" case. Hence the name.

Huh, that's really weird.  If blink-cursor-mode is not the source of the
inconsistencies, then the only explanation is that GNOME somehow behaves
badly if:

  - the back buffer is displayed prior to the title being set.
  - the WM name is changed.
  - another buffer swap happens 400 ms later.

I will try to see if I can reproduce this.

> I am sure, but just to verify, I redid the experiment again. See
> attached files, the naming scheme is the same: two problem cases and
> one "okay" case.

Was blink-cursor-mode turned off, BTW?  If it is on, then potentially
superfluous buffer swaps will end up in the logs once per
blink-cursor-interval and screw them up.

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.