*** This bug is a duplicate of bug 1669444 ***
https://bugs.launchpad.net/bugs/1669444
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/1670876
Title:
Setting MirWindowSpec parameters always causes window's input_region
to be reset
Status in Canonical System Image:
Fix Committed
Status in Mir:
Fix Committed
Status in Mir 0.26 series:
Triaged
Status in MirAL:
Invalid
Status in mir package in Ubuntu:
Fix Released
Bug description:
I've made a quick demo to reproduce this:
https://code.launchpad.net/~gerboland/+git/basic_mir_client/+ref
/cursor-mask-demo
1. launch any mir demo server
2. launch the above demo
3. press 'c' to set the cursor of the window, cursor should become a cross
over the window.
4. press 'm' to set the input region as a subset of the window. You can
observe the input region by moving the cursor over the window, cursor will be a
cross inside the specified region. You can click too, will cause client to
print "click"
5. press 'c' again.
Expected result
no change
Actual result
Input region of surface appears to be reset - cursor is a cross over the
entire window.
I've noticed this behaviour only after this update to QtUbuntu:
https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646
so suspect a bug with the new api only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670876/+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
