This bug was fixed in the package qtmir -
0.5.1+17.04.20170320.1-0ubuntu1
---------------
qtmir (0.5.1+17.04.20170320.1-0ubuntu1) zesty; urgency=medium
[ Alan Griffiths ]
* Reduce dependencies on mirserver by reworking
../Application/mirbuffersgtexture.cpp and
../Application/surfacemanager.cpp
[ Andreas Pokorny ]
* Attach MirInputDeviceId and the MirCookie to input events (LP:
#1536279, #1668692)
[ Daniel d'Andrada ]
* Implement MirSurface::allowClientResize (LP: #1670390)
[ Gerry Boland ]
* Stop MirSurface deleting itself, ensure SurfaceManager alone manages
MirSurface lifetimes. Add SurfaceManager test suite. (LP: #1655644)
* Extend timeouts when running under valgrind
[ Albert Astals Cid, Gerry Boland ]
* Check for find() result not being null before using it
-- Michał Sawicz <michal.saw...@canonical.com> Mon, 20 Mar 2017
21:16:34 +0000
** Changed in: qtmir (Ubuntu)
Status: In Progress => 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/1536279
Title:
Mir does not reset key states when paused or resumed (modifiers get
stuck after VT switching)
Status in Canonical System Image:
Confirmed
Status in Mir:
In Progress
Status in mir package in Ubuntu:
Confirmed
Status in qtmir package in Ubuntu:
Fix Released
Bug description:
Mir switches away from the current VT when ALT+FXX is pressed. During
that key sequence the alt modifier is pressed. While away and mir does
not receive the alt release. When you switch back to mir there is a
chance that mir is not receiving the alt release either.
So switching away and back to mir makes the alt key stick...
Proposed solution:
- track regular keys in mir::input::Seat or in SurfaceDispatcher
- inform client(s) about pause / resume with a focus lost / focus gain event
- attach key state to focus event or send separate key state event
- adapt gdk/qt backends
- fix alt key tracking in unity8 to rely on the provided modifier state
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536279/+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
