GNU bug report logs -
#28589
27.0.50; Emacs screen often becomes blank
Previous Next
Reported by: Katsumi Yamaoka <yamaoka <at> jpl.org>
Date: Mon, 25 Sep 2017 01:03:03 UTC
Severity: normal
Found in version 27.0.50
Done: Philipp Stephani <p.stephani2 <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28589 in the body.
You can then email your comments to 28589 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#28589
; Package
emacs
.
(Mon, 25 Sep 2017 01:03:03 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Katsumi Yamaoka <yamaoka <at> jpl.org>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Mon, 25 Sep 2017 01:03:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
Emacs screen often becomes blank or blinks. This didn't happen
the last weekend, doesn't happen sometimes but often happens.
Changing the window configuration --- scrolling a window, showing
a message of two or more lines in the echo area, etc. --- seems
to cause it. More funny thing is, when two Emacsen are running,
the one of which the frame is not selected becomes blank.
Typing any key in the selected blank frame will help, as if
(sit-for ∞) is running.
Thanks.
In GNU Emacs 27.0.50 (build 1, i686-pc-cygwin, GTK+ Version 3.18.9)
of 2017-09-25 built on localhost
Windowing system distributor 'The Cygwin/X Project', version 11.0.11900000
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#28589
; Package
emacs
.
(Tue, 26 Sep 2017 04:44:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 28589 <at> debbugs.gnu.org (full text, mbox):
On Mon, 25 Sep 2017 10:01:30 +0900, Katsumi Yamaoka wrote:
> Emacs screen often becomes blank or blinks. This didn't happen
> the last weekend, doesn't happen sometimes but often happens.
> Changing the window configuration --- scrolling a window, showing
> a message of two or more lines in the echo area, etc. --- seems
> to cause it. More funny thing is, when two Emacsen are running,
> the one of which the frame is not selected becomes blank.
> Typing any key in the selected blank frame will help, as if
> (sit-for ∞) is running.
Reverting the change c0af83b[1] solves this problem.
[1]
Don't attempt to disable double buffering in newer GTK+ versions
<http://lists.gnu.org/archive/html/emacs-diffs/2017-09/msg00293.html>
> Thanks.
In GNU Emacs 27.0.50 (build 4, i686-pc-cygwin, GTK+ Version 3.18.9)
of 2017-09-26 built on localhost
Windowing system distributor 'The Cygwin/X Project', version 11.0.11900000
Reply sent
to
Philipp Stephani <p.stephani2 <at> gmail.com>
:
You have taken responsibility.
(Tue, 26 Sep 2017 18:32:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Katsumi Yamaoka <yamaoka <at> jpl.org>
:
bug acknowledged by developer.
(Tue, 26 Sep 2017 18:32:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 28589-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Katsumi Yamaoka <yamaoka <at> jpl.org> schrieb am Di., 26. Sep. 2017 um
06:44 Uhr:
> On Mon, 25 Sep 2017 10:01:30 +0900, Katsumi Yamaoka wrote:
> > Emacs screen often becomes blank or blinks. This didn't happen
> > the last weekend, doesn't happen sometimes but often happens.
> > Changing the window configuration --- scrolling a window, showing
> > a message of two or more lines in the echo area, etc. --- seems
> > to cause it. More funny thing is, when two Emacsen are running,
> > the one of which the frame is not selected becomes blank.
> > Typing any key in the selected blank frame will help, as if
> > (sit-for ∞) is running.
>
> Reverting the change c0af83b[1] solves this problem.
>
> [1]
> Don't attempt to disable double buffering in newer GTK+ versions
> <http://lists.gnu.org/archive/html/emacs-diffs/2017-09/msg00293.html>
>
>
Sigh, I had almost expected this would happen. Reverted with 2fa19cc551.
But now we have another time bomb in the codebase:
the gtk_widget_set_double_buffered function is deprecated and will probably
be removed sometime. This makes the migration to a pure GTK+ build even
more pressing.
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#28589
; Package
emacs
.
(Wed, 27 Sep 2017 08:14:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 28589 <at> debbugs.gnu.org (full text, mbox):
> Sigh, I had almost expected this would happen. Reverted with 2fa19cc551.
> But now we have another time bomb in the codebase:
> the gtk_widget_set_double_buffered function is deprecated and will probably
> be removed sometime. This makes the migration to a pure GTK+ build even
> more pressing.
Looks like the decisive blow, indeed. Admittedly, inhibiting double
buffering was a gross hack too. But I doubt Jan had any alternative
solutions at hand when he coded that.
Do I understand correctly that the entire effect of setting double
buffering off is encapsuled in the case where a GDK_EXPOSE event is
handled?
martin
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 25 Oct 2017 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 6 years and 184 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.