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?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
0.23 xapps need interaction to start in pocket-desktop
Status in Mir:
In Progress
Status in Mir 0.23 series:
In Progress
Status in Mir 0.24 series:
In Progress
Status in mir package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
in 0.23 the xapps need some interaction to get the applications to
start. 0.23 is blocked pending fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
