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/1669444 Title: [regression] OSK input shaping no longer works correctly 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 Status in qtmir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this more usable at present) 2) Click in an input field 3) Move the mouse over the keyboard 4) Attempt to click on the app again Expected result: The mouse click should be passed through to the app Actual result: The click is swallowed by the keyboard surface instead. However, it is still possible to click on the app if this is done prior to the mouse entering the visible keyboard area. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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
