This bug was fixed in the package mir - 0.1.6+14.04.20140310-0ubuntu1
---------------
mir (0.1.6+14.04.20140310-0ubuntu1) trusty; urgency=medium
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Importance: Undecided => Medium
** Changed in: mir (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1281938
Title:
Mir shows an old frame on client startup (for Mesa GL clients)
Status in Mir:
Fix Released
Status in “mesa” package in Ubuntu:
Triaged
Status in “mir” package in Ubuntu:
Fix Released
Bug description:
Mir shows an old frame on client startup.
Test case (1):
1. Start and stop one client at a time:
bin/mir_demo_client_egltriangle -s 500x500
bin/mir_demo_client_eglflash -s 500x500
...
Expected: Each client only shows its own frames
Observed: The first frame of each client seems to be the last frame of the
_previous_ client.
Test case(2) - more definitive but requires hacking:
1. Insert a long sleep in your client code just before eglSwapBuffers
Expected: The Mir server never shows the client till after the sleep has
finished.
Observed: The Mir server composites the client immediately on startup, with
old/invalid pixel data. It only gets replaced with a valid frame after the
sleep finishes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1281938/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
