Actually Robert slipped his proposed fix just in time into the 0.11.0 release. And the 0.12 branch inherits from that...
------------------------------------------------------------ revno: 2287 tags: v0.11.0 committer: Robert Carr <[email protected]> branch nick: 0.11 timestamp: Mon 2015-02-09 13:07:25 -0800 message: Cherrypick lp:~mir-team/mir/catch-exceptions-at-android-driver-boundary ------------------------------------------------------------ Sadly, this bug was reported against the same release it's meant to be fixed in. Although it's hard to tell what came first because the pre- release with the bug and the apparent fix both occurred on the same day. It's not yet clear if the bug is fixed in any branch yet. ** Changed in: mir Status: Fix Committed => Incomplete ** No longer affects: mir/0.12 ** Changed in: mir Milestone: 0.13.0 => 0.11.0 ** Changed in: mir (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425307 Title: [regression] Exception when running phablet-screenshot (mako/vivid 110) [std::exception::what: Attempt to set swap interval on screencast is invalid] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1425307/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
