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

Previous Next

Full log

Message #113 received at 61667 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 61667 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>, gregory <at> heytings.org
Subject: Re: bug#61667: 29.0.60; Failure to redisplay
Date: Thu, 23 Feb 2023 16:01:12 +0200

[Message part 1 (text/plain, inline)]

On 23/02/2023 15:13, Po Lu wrote:
> Dmitry Gutov <dgutov <at> yandex.ru> writes:
> 
>> Most of all I'm worried that this is some kind of bug in GNOME, which
>> I don't have a lot of alternatives to.
> 
> Likely not, but let's make sure.  With the printf instrumentation
> present, what happens if you pipe the instrumentation to a file,

Then it reproduces. But since I'm not seeing the output live, I can't 
answer the question "what is printed when the problem happens".

I'm attaching four logs anyway: alternating between when the problem 
reproduced, and when it did not. Otherwise the scenario was almost or 
exactly the same, up to the characters typed.

out1.txt and out3.txt - reproduced.
out2.txt and out4.txt - did not.

> or run
> Emacs from the Linux text console, as opposed to inside a window
> redirected by GNOME's compositing manager?

Not sure what you mean. 'emacs -nw'? Or run a separate X server and 
Emacs inside it, launched from a tty?

I'd have to look up how to do that. Last type I typed 'startx' was >10 
years ago.

[out1.txt (text/plain, attachment)]

[out2.txt (text/plain, attachment)]

[out3.txt (text/plain, attachment)]

[out4.txt (text/plain, attachment)]

Previous Next

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