[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-07-10 Thread Daniel van Vugt 
** Changed in: mir
   Status: Fix Committed => 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:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-07-10 Thread Launchpad Bug Tracker 
This bug was fixed in the package mir - 0.27.0+17.10.20170630-0ubuntu1

---
mir (0.27.0+17.10.20170630-0ubuntu1) artful; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.27.0 (https://launchpad.net/mir/+milestone/0.27.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 44
  . mircommon ABI unchanged at 7
  . mirplatform ABI bumped to 61
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 13
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI bumped to 7
  . mircore ABI unchanged at 1
- Enhancements:
  . Mostly groundwork required to support major enhancements coming in
future Mir versions.
  . Removed android-input and eliminated the entire "3rd_party/" subtree.
Now the Mir source tree contains original code only.
  . Added mir_prompt_session_new_fds_for_prompt_providers_sync API.
  . mirout: Added load and save options for keeping display configs
on disk.
  . mirout: Added "--" support for applying configuration changes under
Unity8.
  . Fixed failure of DRM hardware cursor {hide(); show(image);}
  . Added server option: "--cursor software" (MIR_SERVER_CURSOR=software)
  . Added letterboxing/black bars support to the GL renderer in preparation
for generic output cloning.
  . Added client API for getting the logical size of an output.
  . Migrated MirCookie to use SHA-256.
  . Ensure RealKMSOutputConfiguration stays in sync with actual hardware
state.
  . Added support for drag-and-drop.
  . Lots of other client API enhancements.
  . Minor clean-ups, optimizations and dead code removal.
  . Added support for building on Ubuntu 17.10 artful.
  . Update example code to use undeprecated API.
  . mesa-kms: Support hardware cursors in hybrid setups.
  . Rework and publish the graphics platform APIs
- Bugs fixed:
  . [enhancement] Make able to get version information from client /
server APIs (LP: #1195540)
  . Touch screen coordinates don't rotate with the screen (LP: #1349660)
  . Subpixel order not included in Mir display information (LP: #1393578)
  . [enhancement] Missing client API for relative surface movement (e.g.
dragging client-decorated windows) (LP: #1420334) . Mir does not reset
key states when paused or resumed (modifiers get stuck after VT
switching) (LP: #1536279)
  . NBS never uses mc::MultiMonitorMode::single_monitor_fast, even when
only a single monitor is plugged in (LP: #1561418)
  . Inconsistent behaviour of Num Lock (LP: #1588237)
  . A scaled (not panned or clipped) mirror/clone mode is desired
(LP: #1639226)
  . Rotating an output left or right without restarting the
compositor distorts the image (LP: #1643488)
  . support display scaling slider in unity8 (LP: #1645372)
  . [ FAILED ] NestedInputWithMouse.mouse_pointer_coordinates_in_nested_
server_are_accumulated (LP: #1646375)
  . [ FAILED ] NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_
host_server (LP: #1646558)
  . abi_check doesn't check mircore (LP: #1649354)
  . [testsfail] PromptSessionClientAPI.client_pid_is_associated_with_
session hangs and times out (LP: #1655929)
  . EDID does not change when hotplugging a monitor (LP: #1660017)
  . [regression] Mir 0.26.0 - spinner loading animation, minimize, maximize
too fast (LP: #1661072)
  . [regression] Unity8 stutters constantly (like half frame rate) using
Mir 0.26.0 (LP: #1661128)
  . [regression] mir_demo_server refuses to quit on Ctrl+Alt+Backspace or
Ctrl+C in its terminal (deadlock in DefaultInputDeviceHub::add_device)
(LP: #1661151)
  . [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)
  . [ FAILED ] DefaultInputManagerTest.forwards_pause_continue_state_
changes_to_platform (LP: #1661187)
  . [regression] Segfault on detect_fd_leaks during acceptance tests (in
DisplayConfiguration/{DisplayFormatSetting,DisplaySubpixelSetting})
(LP: #1661498)
  . [regression] Nested server segfaults or rapidly logs exceptions when a
fullscreen client starts [in mir_presentation_chain_set_dropping_mode
... std::exception::what: Operation not permitted] (LP: #1661508)
  . [regression] Windowed clients of nested servers are all black
(LP: #1661521)
  . mir_window_request_persistent_id_sync seg faults when called twice
(LP: #1661704)
  . mir_acceptance_tests now takes 10 seconds longer (in r4002 compared to
r4001) (LP: #1662044)
  . Mir graphics platform ABI broke in series 0.26 but

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-06-15 Thread Launchpad Bug Tracker 
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2818

-- 
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:
  Fix Committed
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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-06-08 Thread Launchpad Bug Tracker 
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2806

-- 
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:
  Fix Committed
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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-04-03 Thread Launchpad Bug Tracker 
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683

-- 
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:
  Fix Committed
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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-03-28 Thread mir-ci-bot 
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0

** Changed in: mir
   Status: In Progress => Fix Committed

-- 
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:
  Fix Committed
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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-03-23 Thread Launchpad Bug Tracker 
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   Mon, 20 Mar 2017
21:16:34 +

** 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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-03-13 Thread Michał Sawicz 
** Project changed: qtmir => qtmir (Ubuntu)

-- 
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:
  In Progress

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-03-09 Thread Launchpad Bug Tracker 
** Branch linked: lp:~andreas-pokorny/mir/fix-1536279

-- 
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 QtMir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-02-28 Thread Andreas Pokorny 
** Changed in: qtmir
   Status: Confirmed => In Progress

-- 
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 QtMir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-02-28 Thread Launchpad Bug Tracker 
** Branch linked: lp:~andreas-pokorny/qtmir/store-and-recover-cookie-
and-input-device-id

-- 
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 QtMir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-02-28 Thread Andreas Pokorny 
** Changed in: qtmir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: qtmir
   Status: New => Confirmed

-- 
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 QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-02-21 Thread Cemil Azizoglu 
** Changed in: mir
   Importance: Medium => High

-- 
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 QtMir:
  New
Status in mir package in Ubuntu:
  Confirmed

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

[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed (modifiers get stuck after VT switching)

2017-02-19 Thread Daniel van Vugt 
** Summary changed:

- Mir does not reset key states when paused or resumed
+ Mir does not reset key states when paused or resumed (modifiers get stuck 
after VT switching)

-- 
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 QtMir:
  New
Status in mir package in Ubuntu:
  Confirmed

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