GNU bug report logs - #18451
24.4.50; 'toggle-frame-fullscreen' can cut off minibuffer

Previous Next

Package: emacs;

Reported by: dev <at> mattleach.net

Date: Thu, 11 Sep 2014 16:42:02 UTC

Severity: normal

Tags: moreinfo

Found in version 24.4.50

Done: martin rudalics <rudalics <at> gmx.at>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: Matthew Leach <matthew <at> mattleach.net>
Cc: 18451 <at> debbugs.gnu.org
Subject: bug#18451: 24.4.50; 'toggle-frame-fullscreen' can cut off minibuffer
Date: Tue, 16 Sep 2014 20:38:21 +0200
Hello.

14 sep 2014 kl. 15:32 skrev Matthew Leach <matthew <at> mattleach.net>:

> Jan Djärv <jan.h.d <at> swipnet.se> writes:
> 
>> Hello.
> 
> Hi Jan,
> 
> 
> [...]
> 
>> If you compile Emacs yourself, you can debug this by tracing the
>> ConfigureNotify Emacs gets and/or the calls to change_frame_size and
>> xg_frame_resized.  Obviously some call is either not made or made with
>> the wrong parameters.  It may be a race condition so that Emacs gets
>> ConfigureNotify out of sequence.
> 
> I have added trace prints in the functions that you suggested and things
> do look different when the bug occurs.
> 
> 
> The following trace is printed when the resize happens correctly (the
> trace seems to be the same between bug-free resize operations).
> 
> ConfigureNotify event received.
> ConfigureNotify event received.
> ConfigureNotify event received.
> xg_frame_resized(0x6896f8, 1366, 768);
> change_frame_size(0x6896f8, 1350, 768, 0, 1, 0, 1);
> change_frame_size(0x6896f8, 1350, 768, 0, 0, 0, 1);
> ConfigureNotify event received.
> ConfigureNotify event received.
> ConfigureNotify event received.
> ConfigureNotify event received.
> xg_frame_resized(0x6896f8, 679, 729);
> change_frame_size(0x6896f8, 663, 729, 0, 1, 0, 1);
> change_frame_size(0x6896f8, 663, 729, 0, 0, 0, 1);
> ConfigureNotify event received
> 
> This is the trace when the bug occurs (again, the trace is consistent
> between buggy resize operations):
> 

The question is where does change_frame_size get called from from if they are not from xg_frame_resized?

As a long shot, try removing this line:

do_pending_window_change (0);

in xg_frame_resized.

	Jan D.


> ConfigureNotify event received.
> ConfigureNotify event received.
> change_frame_size(0x6896f8, 1350, 768, 0, 1, 0, 1);
> ConfigureNotify event received.
> ConfigureNotify event received.
> change_frame_size(0x6896f8, 1350, 768, 0, 0, 1, 1);
> ConfigureNotify event received.
> ConfigureNotify event received.
> ConfigureNotify event received.
> xg_frame_resized(0x6896f8, 679, 729);
> change_frame_size(0x6896f8, 663, 729, 0, 1, 0, 1);
> change_frame_size(0x6896f8, 663, 729, 0, 0, 0, 1);
> ConfigureNotify event received.
> ConfigureNotify event received.
> xg_frame_resized(0x6896f8, 672, 720);
> change_frame_size(0x6896f8, 656, 720, 0, 1, 0, 1);
> change_frame_size(0x6896f8, 656, 720, 0, 0, 0, 1);
> 
> 
> xg_frame_resized doesn't seem to be called on the buggy trace when entering
> full-screen. Any ideas where else I could look?
> -- 
> Matt





This bug report was last modified 10 years and 101 days ago.

Previous Next


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