This bug was fixed in the package miral - 1.3.0+17.04.20170303-0ubuntu1 --------------- miral (1.3.0+17.04.20170303-0ubuntu1) zesty; urgency=medium
* New upstream release 1.3.0 (https://launchpad.net/miral/+milestone/1.3) - ABI summary: . miral ABI unchanged at 2 - Enhancements: . [libmiral] Support for workspaces . [libmiral] Add miral::WindowManagerTools::focus_prev_within_application (LP: #1668562) . [libmirclientcpp] A better description of libmirclientcpp-dev . [libmirclientcpp] Add RAII wrapper for MirDisplayConfig. . [libmirclientcpp] Prevent accidental double-release by deleting release functions for handle classes . [miral-shell] Example workspaces implementation . [miral-shell] Use background to show keyboard shortcuts - Bugs fixed: . [libmiral] Join internal client threads before server shutdown (LP: #1668651) . [miral-shell] Workaround for crash on exit (LP: #1667645) -- Alan Griffiths <alan.griffi...@canonical.com> Fri, 03 Mar 2017 10:19:14 +0000 ** Changed in: miral (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1667645 Title: If the only surface in a session cannot take focus the server crashes Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in MirAL: Fix Committed Status in mir package in Ubuntu: Triaged Status in miral package in Ubuntu: Fix Released Bug description: The problem is in ms::ApplicationSession::surface_after() it can dereference the surfaces.end() iterator. Original description: $ bin/miral-desktop ... terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >' what(): surface_after: surface is not a member of this session Aborted (core dumped) Using tiling WM doesn't exhibit this problem: $ bin/miral-desktop --window-manager tiling I would guess this is something to do with the recent addition of wallpaper. And possibly due to this test box being slow (14 years old), not due to Xenial/Mir 21.0. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1667645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
