It's worth remembering a client can always (rightly or wrongly) refuse to render a new frame (e.g. it might freeze or it might be by design). It is always the server's responsibility to render the pixels of the last frame from the client correctly, never stretched out of proportion.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1649662 Title: resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 + proposed mir 0.25 miral 0.25 unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 [installed,automatic] steps: 1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for ex). if you are not sure how to launch a gtk3 app run "ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch <appid>" 2) resize the window (the context gets stretched in a weird way and input doesn't work anymore) see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
