XWayland missing root window properties after start
When I first start Chrome after logging in, it has thick square window borders (just like GTK3 does when frame extents are unsupported). If I exit Chrome and run it again, then it finally has proper CSD borders.
Apparently this is due to the root X window missing all of the _NET_*
and _GTK_*
properties when the first X client looks at it – they only appear when queried the second time.
$ xprop -root
PULSE_COOKIE(STRING) = "2c9a4fd2[...]29e71539"
PULSE_SERVER(STRING) = "{85204cb86d616b56fbe44fbb7fd816df}unix:/run/user/1000/pulse/native"
PULSE_ID(STRING) = "1000@85204cb86d616b56fbe44fbb7fd816df/75465"
AT_SPI_BUS(STRING) = "unix:path=/tmp/dbus-oOuBkh2pwH,guid=8b840e4442c11d53321e2edf6228aff4"
XIM_SERVERS(ATOM) = @server=ibus
RESOURCE_MANAGER(STRING) = "XTerm*vt100.metaSendsEscape:\ttrue\nXTerm*vt100.translations:\t#override \\n Shift Ctrl <Key>C: copy-selection(CLIPBOARD) \\n Shift Ctrl <Key>V: insert-selection(CLIPBOARD) \\n Shift Ctrl <Key>N: spawn-new-terminal() \\n\nXTerm.backarrowKeyIsErase:\ttrue\nXTerm.ptyInitialErase:\ttrue\nXTerm.termName:\txterm-256color\nXcursor.size:\t24\nXcursor.theme:\tAdwaita\nXft.antialias:\t1\nXft.dpi:\t96\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\tnone\n"
GDK_VISUALS(INTEGER) = 291, 278
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""
Running the same xprop -root
two seconds later has all of the expected _NET_*
properties.
This is GNOME 41.4 on Wayland (with Chrome being the only X11 program here), I haven't verified this on GNOME 42 yet, but on IRC it was confirmed to affect GNOME 42.rc as well.