This bug was fixed in the package mir - 0.12.0+15.04.20150228-0ubuntu1
---
mir (0.12.0+15.04.20150228-0ubuntu1) vivid; urgency=medium
[ Alberto Aguirre ]
* New upstream release 0.12.0 (https://launchpad.net/mir/+milestone/0.12.0)
- Packaging changes:
. Client platform
** Changed in: mir
Milestone: 0.13.0 = 0.12.0
** No longer affects: mir/0.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421255
Title:
[regression] Deadlock in TimeoutFrameDroppingPolicy
** Changed in: mir/0.12
Status: Fix Committed = Fix Released
** Changed in: mir
Status: Fix Committed = 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/1421255
Title:
Alberto says this was a regression, introduced in 0.9.0 with glib main
loop.
** Summary changed:
- Deadlock in TimeoutFrameDroppingPolicy logic results in frozen unity8
+ [regression] Deadlock in TimeoutFrameDroppingPolicy logic results in frozen
unity8
** Tags added: regression
** Also
