This bug was fixed in the package qtmir - 0.4.1+14.10.20140815-0ubuntu1
---------------
qtmir (0.4.1+14.10.20140815-0ubuntu1) utopic; urgency=low
[ Daniel d'Andrada ]
* MirSurfaceItem: always try to consume new mir frames Otherwise those
frames will get dropped and MirSurfaceItem will therefore never use
them, being left displaying an old, stale, frame until the
application renders again.This could happen for instance if an
application was rendering between the time the Application object
goes to Suspended state and the actual process getting SIG_STOPPED
(ie, suspended for real). Frames rendered in this interval were
getting dropped and once that app was resumed and its MirSurfaceItem
brought to front the user would see an old stale frame until some
new event caused the application to render a new frame (e.g. an
input event) (LP: #1353374)
-- Ubuntu daily release <[email protected]> Fri, 15 Aug 2014
17:13:24 +0000
** Changed in: qtmir (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353374
Title:
Last dash frame not posted to display
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1353374/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
