This is a very old issue. On surface creation a mir callback is called where qtmir can modify the parameters of a surface about to be created, such as its size. Gerry tried in the past to connect this callback to unity8 so the latter could set the size properly, but it led to some horrible threading-related crashes and thus pulled out.
If I'm not mistaken nowadays that callback (MirWindowManagerImpl::add_surface I tink) simply defaults to the screen size, which is a fine default for phone but evidently not for desktop. And this old issue was made more evident now that we no longer stretch windows in shell, so on desktop you see a fullscreen window for a splitsecond before the app responds to the resize. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1532974 Title: large window flicker on ubuntu apps launching in window mode Status in The Avila project: New Status in Canonical System Image: Triaged Status in canonical-pocket-desktop: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I don't recall ever seeing this, and I believe i would have noticed, so I think this is a regression This only seems to occur for ubuntu apps (not puritine/xmir apps) This is probably best demonstrated with the Clock app because of the trusted prompt - which in the clock app case actually holds the large window on screen steps to repro 1) connect bt mouse 2) connect slimport to device 3) launch clock app (or any other ubuntu app and keep your eyes on the screen for the flicker) also, tested this on both n7 and n4, it occurs on both To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1532974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
