unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thiago Melo <tmdmelo@gmail.com>
To: 64923@debbugs.gnu.org
Subject: bug#64923: 29.1; white background glitch with new graphical frames
Date: Fri, 28 Jul 2023 22:19:12 +0000	[thread overview]
Message-ID: <CABpoeKg5GU_pHhuStYjP3dsGeZqXeFNecJggkP2wN4wzvL5m9w@mail.gmail.com> (raw)

Under the conditions specified below, new graphical frames are
completely white until a redrawing is forced (usually by resizing the
frame):

Emacs built with:

- No toolkit OR Lucid (--with-x-toolkit=no OR --with-x-toolkit=lucid)
- Cairo (--with-cairo)
- Double buffering (--with-xdbe)

Plus:

- Without an X window manager OR using TinyWM
- No toolkit builds: when scrollbar is disabled before creating the frame
- Lucid builds: when scrollbar AND menubar are disabled before
creating the frame

Affects `emacs -Q'.  Tested on Debian GNU/Linux 12.1 (Bookworm).

Issue started happening since commit
e361d0d7e5d3db8575d5d8673012aa4d7448ee54 (Tue Mar 1 20:15:02 2022
+0800, "Add PropertyChangeMask to the standard event set").  Found via
bisect.

Also, out of all (non-toy) window managers I've tested so far
(awesome, dwm, fluxbox, fvwm2, herbstluftwm, i3, twm, xfwm4; all from
stock Debian repository and with default config), only awesome wm
shows direct signs of this issue, and only when set to use floating
windows.  However, in this condition, new frames have a white
background only in areas without text, regardless of theme (more
evident with a dark theme, eg: `M-x load-theme' -> `wombat').

I suspect this issue might be related to bug#64846 as well.





             reply	other threads:[~2023-07-28 22:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 22:19 Thiago Melo [this message]
2023-07-29  0:20 ` bug#64923: 29.1; white background glitch with new graphical frames Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-29 10:34   ` Thiago Melo
2023-07-29 11:18     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-29 22:52       ` Thiago Melo
2023-07-30  2:08         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-30  5:21           ` Eli Zaretskii
2023-07-30  5:59             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-30  9:23               ` Eli Zaretskii
2023-07-30  9:22             ` Eli Zaretskii
2023-07-30 12:11               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-30 13:07           ` Thiago Melo
2023-07-31  0:40             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABpoeKg5GU_pHhuStYjP3dsGeZqXeFNecJggkP2wN4wzvL5m9w@mail.gmail.com \
    --to=tmdmelo@gmail.com \
    --cc=64923@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).