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 protected]>
[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 protected]>
[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 protected]> Tue, 20 May 2014
12:58:36 +0000
** Changed in: unity-mir (Ubuntu)
Status: Confirmed => 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/1305128
Title:
Apps don't always get focused when started with upstart-app-launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/content-hub/+bug/1305128/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
