This bug was fixed in the package mir - 0.26.2+17.04.20170322.1-0ubuntu1 --------------- mir (0.26.2+17.04.20170322.1-0ubuntu1) zesty; urgency=medium
[ Daniel van Vugt ] * New upstream release 0.26.2 (https://launchpad.net/mir/+milestone/0.26.2) - Bugs fixed: . EDID does not change when hotplugging a monitor (LP: #1660017) . [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field. h:1408] CHECK failed: (index) < (current_size_) (LP: #1661163) . Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle() (LP: #1664760) . Nested servers (Unity8) periodically stutter (half frame rate) with Mir 0.26.1 (LP: #1666372) . Don't dereference the end iterator in ms::ApplicationSession:: surface_after() (LP: #1667645) . [regression] OSK input shaping no longer works correctly (LP: #1669444) . Setting MirWindowSpec parameters always causes window's input_region to be reset (LP: #1670876) . Subpixel order not included in Mir display information (LP: #1393578) . Presentation chains should support various swap interval modes (LP: #1673533) . Need an extension for GBM buffers to replace mir_buffer_get_buffer_package() (LP: #1673534) . Seg fault on detect_fd_leaks (LP: #1661498) -- Cemil Azizoglu <cemil.azizo...@canonical.com> Wed, 22 Mar 2017 04:54:19 +0000 ** Changed in: mir (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 Released Status in mir package in Ubuntu: Fix Released 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