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/1666372 Title: Nested servers (Unity8) periodically stutter (half frame rate) with Mir 0.26.1 Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Fix Released Bug description: Nested servers periodically stutter (half frame rate) with Mir 0.26.1 On an old laptop, it's about half the time stuttering and half the time smooth. On a fast desktop, it only stutters occasionally like when a large blur is active. It seems the problem is Mir's predictive bypass optimization conflicting with the new client-side vsync optimization. Both are correct and desirable when used alone, but when used together they conflict, presumably because the former requires perfect vsync phase and the latter lacks correct vsync phase (which is still an exercise for later). A workaround to get more reliably smooth frame rates is to create a file: /etc/lightdm/lightdm.conf.d/foo.conf with contents: [Seat:*] unity-compositor-command=/usr/sbin/unity-system-compositor --composite-delay=0 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666372/+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
