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

Previous Next

Full log

View this message in rfc822 format

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 61667 <at> debbugs.gnu.org
Subject: bug#61667: 29.0.60; Failure to redisplay
Date: Tue, 21 Feb 2023 12:43:29 +0200

On 21/02/2023 12:19, Po Lu wrote:
> Dmitry Gutov <dgutov <at> yandex.ru> writes:
> 
>> Hovering the mouse over the mode-line does trigger the necessary
>> redisplay. Alt-Tabbing to another window and then back also does
>> that. Is that relevant?
>>
>> Simply moving the mouse (not over the mode-line) doesn't help.
>>
>> The refresh can also happen on its own, in 1-2 seconds.
> 
> I think this isn't a problem with the GLib input code then.
> 
> Alt-tabbing makes the X event reading code explicitly ask for a
> redisplay.  If you build --with-checking=yes,glyphs and call
> `trace-redisplay', what happens when the redisplay does not happen?

Okay, I've rebuilt with --enable-checking=glyphs.

With --eval '(trace-redisplay t)', redisplay always happens. ;-(

That's not the effect of 'checking', though -- I can still repro if I 
don't turn on redisplay tracing (which prints stuff in the background 
window; maybe it's relevant, maybe it's not).

Previous Next

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