unity8 7.86+14.10.20140429.2-0ubuntu1 crashes on recent utopic images

[Timo Jyrinki]

Unity8 crashes when running the test suites, as visible eg. at:
http://ci.ubuntu.com/smokeng/utopic/touch/mako/8:20140502:20140501/7837/

These started in image #5 (http://people.canonical.com/~ogra/touch-image-stats/5.changes) and have continued since.

This mailing list quote is related:
---
Here's all I could get out of the .crash:

--- source code stack trace ---
#0 0xb439ab54 in mir::DisplayServer::stop() () from
/usr/lib/arm-linux-gnueabihf/libmirserver.so.18
#1 0xb6496b5c in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
---

Although unlike stated in that e-mail, the crashes did not disappear with image #6.

[Michał Sawicz (saviq)]

Reducing Importance as this is on-exit, non-user-facing crash. Will fix nevertheless.

[Michał Sawicz (saviq)]

Offending commit in unity-mir:

http://bazaar.launchpad.net/~mir-team/unity-mir/trunk/revision/216

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:unity-mir/devel at revision 220, scheduled for release in unity-mir, milestone Unknown

[Launchpad Janitor (janitor)]

This bug was fixed in the package unity-mir - 0.4+14.10.20140520-0ubuntu1

---------------
unity-mir (0.4+14.10.20140520-0ubuntu1) utopic; urgency=low

  [ Tarmac ]
  * Merge devel at rev 222. (Fix crash on shell shutdown; Refactor app
    shutdown) 2014-05-06 Gerry Boland <email address hidden>
            [220] Fix crash on Mir-initiated shutdown, where stop() was
    being         called on an already shutting-down server.         Mir
    initiates shutdown on SIGINT & SIGTERM, need to distinguish that
            shutdown from a client-initiated shutdown. Do this by
    installing a         custom signal handler that is run after Mir's
    initiate-shutdown         handler is called, so that we only call
    server.stop() on a client-         initiated shutdown. (LP:
    #1305128, #1315251)

  [ Kevin Gunn ]
  * Merge devel at rev 222. (Fix crash on shell shutdown; Refactor app
    shutdown) 2014-05-06 Gerry Boland <email address hidden>
            [220] Fix crash on Mir-initiated shutdown, where stop() was
    being         called on an already shutting-down server.         Mir
    initiates shutdown on SIGINT & SIGTERM, need to distinguish that
            shutdown from a client-initiated shutdown. Do this by
    installing a         custom signal handler that is run after Mir's
    initiate-shutdown         handler is called, so that we only call
    server.stop() on a client-         initiated shutdown. (LP:
    #1305128, #1315251)
 -- Ubuntu daily release <email address hidden> Tue, 20 May 2014 12:58:36 +0000