| 2016-01-20 17:06:43 |
Andreas Pokorny |
bug |
|
|
added bug |
| 2016-01-21 13:18:14 |
Andreas Pokorny |
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... |
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:
- Make input platforms aware of pause and resume state changes
- on pause make evdev platform send release for all still pressed buttons
- on resume make evdev platform send press for all currently pressed buttons |
|
| 2016-01-21 15:06:36 |
Daniel van Vugt |
tags |
|
input |
|
| 2016-01-29 10:05:47 |
Daniel van Vugt |
bug task added |
|
qtmir |
|
| 2016-03-23 13:56:06 |
Michał Sawicz |
bug task added |
|
canonical-devices-system-image |
|
| 2016-03-23 13:56:27 |
Michał Sawicz |
canonical-devices-system-image: assignee |
|
Stephen M. Webb (bregma) |
|
| 2016-03-24 11:42:33 |
Jean-Baptiste Lallement |
canonical-devices-system-image: status |
New |
Confirmed |
|
| 2016-03-24 11:42:38 |
Jean-Baptiste Lallement |
canonical-devices-system-image: importance |
Undecided |
Medium |
|
| 2016-04-04 16:34:06 |
Cemil Azizoglu |
mir: milestone |
|
0.22.0 |
|
| 2016-04-04 16:34:39 |
Cemil Azizoglu |
mir: assignee |
|
Andreas Pokorny (andreas-pokorny) |
|
| 2016-04-08 09:54:30 |
Andreas Pokorny |
mir: status |
New |
In Progress |
|
| 2016-04-08 09:56:52 |
Andreas Pokorny |
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:
- Make input platforms aware of pause and resume state changes
- on pause make evdev platform send release for all still pressed buttons
- on resume make evdev platform send press for all currently pressed buttons |
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
- inform client(s) about pause / resume with a focus lost / focus gain event
- attach key state to focus events
- adapt gdk/qt backends
- fix alt key tracking in unity8 to rely on the provided modifier state |
|
| 2016-04-08 12:31:47 |
Andreas Pokorny |
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
- inform client(s) about pause / resume with a focus lost / focus gain event
- attach key state to focus events
- adapt gdk/qt backends
- fix alt key tracking in unity8 to rely on the provided modifier state |
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:
- add something to the input platform API, so that keyboard devices can expose a current key state..
- 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 events
- adapt gdk/qt backends
- fix alt key tracking in unity8 to rely on the provided modifier state |
|
| 2016-04-12 13:24:36 |
Andreas Pokorny |
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:
- add something to the input platform API, so that keyboard devices can expose a current key state..
- 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 events
- adapt gdk/qt backends
- fix alt key tracking in unity8 to rely on the provided modifier state |
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 |
|
| 2016-04-21 06:12:11 |
Alberto Aguirre |
mir: milestone |
0.22.0 |
0.23.0 |
|
| 2016-04-29 16:56:16 |
Kevin DuBois |
mir: milestone |
0.23.0 |
0.24.0 |
|
| 2016-07-07 13:22:09 |
Kevin DuBois |
mir: milestone |
0.24.0 |
0.25.0 |
|
| 2016-07-20 02:32:52 |
Daniel van Vugt |
bug task added |
|
mir (Ubuntu) |
|
| 2016-08-03 02:25:14 |
Launchpad Janitor |
mir (Ubuntu): status |
New |
Confirmed |
|
| 2016-08-03 02:25:58 |
Daniel van Vugt |
mir: importance |
Undecided |
Medium |
|
| 2016-08-03 02:26:01 |
Daniel van Vugt |
mir (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-11-07 18:20:15 |
Brandon Schaefer |
mir: milestone |
0.25.0 |
0.26.0 |
|
| 2017-01-15 11:19:27 |
Daniel van Vugt |
mir: milestone |
0.26.0 |
1.0.0 |
|
| 2017-02-20 01:46:55 |
Daniel van Vugt |
summary |
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) |
|
| 2017-02-21 17:10:38 |
Cemil Azizoglu |
mir: importance |
Medium |
High |
|
| 2017-02-28 20:03:19 |
Andreas Pokorny |
qtmir: assignee |
|
Andreas Pokorny (andreas-pokorny) |
|
| 2017-02-28 20:03:27 |
Andreas Pokorny |
qtmir: status |
New |
Confirmed |
|
| 2017-02-28 20:07:30 |
Launchpad Janitor |
branch linked |
|
lp:~andreas-pokorny/qtmir/store-and-recover-cookie-and-input-device-id |
|
| 2017-02-28 20:16:16 |
Andreas Pokorny |
qtmir: status |
Confirmed |
In Progress |
|
| 2017-03-09 11:54:28 |
Launchpad Janitor |
branch linked |
|
lp:~andreas-pokorny/mir/fix-1536279 |
|
| 2017-03-13 17:47:00 |
Michał Sawicz |
affects |
qtmir |
qtmir (Ubuntu) |
|
| 2017-03-24 01:58:37 |
Launchpad Janitor |
qtmir (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-03-28 12:21:37 |
Mir CI Bot |
mir: status |
In Progress |
Fix Committed |
|
| 2017-04-04 02:28:44 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683 |
|
| 2017-06-08 09:43:53 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-artful-2806 |
|
| 2017-06-15 13:55:23 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-zesty-2818 |
|
| 2017-07-10 19:53:54 |
Launchpad Janitor |
mir (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2017-07-11 04:10:56 |
Daniel van Vugt |
mir: status |
Fix Committed |
Fix Released |
|
