Mir

Comment 2 for bug 1584784

Well, for some reason, this appears to be where the (gedit) window gets realized in our existing release:

Atom _NET_WM_NAME = 267
Atom _NET_WM_WINDOW_TYPE = 295
Realize window 0xabaa7a98 "": 985x1093 +0+0 parent=0xab8dadc8
 depth=24 redir=0 type=0 class=1 visibility=3 viewable=1
 override=1 _NET_WM_WINDOW_TYPE=0 WM_TRANSIENT_FOR=(nil)
Atom UTF8_STRING = 268
Realize window 0xabaadca0 "gedit": 985x1093 +0+0 parent=0xabaa7a98
 depth=24 redir=0 type=0 class=1 visibility=3 viewable=1
 override=0 _NET_WM_WINDOW_TYPE=254 WM_TRANSIENT_FOR=(nil)
Realize window 0xabaadfa0 "": 1x1 -1-1 parent=0xabaadca0
 depth=0 redir=0 type=2 class=2 visibility=3 viewable=0
 override=0 _NET_WM_WINDOW_TYPE=0 WM_TRANSIENT_FOR=(nil)
Atom _NET_WM_WINDOW_TYPE_NORMAL = 254

which doesn't happen in the 0.23 silo. The server will continue to schedule redraws, and resizing the window seems to cause it to realize.

What events lead up to a window being realized on startup?