2017-03-23 11:05:04 |
Michał Sawicz |
bug |
|
|
added bug |
2017-03-23 11:05:18 |
Michał Sawicz |
bug task added |
|
canonical-devices-system-image |
|
2017-03-23 11:05:24 |
Michał Sawicz |
canonical-devices-system-image: status |
New |
Confirmed |
|
2017-03-23 11:05:28 |
Michał Sawicz |
canonical-devices-system-image: status |
Confirmed |
Triaged |
|
2017-03-23 11:05:29 |
Michał Sawicz |
canonical-devices-system-image: importance |
Undecided |
High |
|
2017-03-23 11:05:31 |
Michał Sawicz |
canonical-devices-system-image: assignee |
|
Michał Sawicz (saviq) |
|
2017-03-23 11:05:35 |
Michał Sawicz |
canonical-devices-system-image: milestone |
|
u8c-z |
|
2017-03-23 11:05:42 |
Michał Sawicz |
bug task added |
|
qtmir (Ubuntu) |
|
2017-03-23 11:14:50 |
Albert Astals Cid |
bug |
|
|
added subscriber Albert Astals Cid |
2017-03-23 12:40:00 |
Gerry Boland |
bug task added |
|
mir (Ubuntu) |
|
2017-03-23 12:42:14 |
Gerry Boland |
summary |
Unity8 spins for a long time after being on an inactive vt |
Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) |
|
2017-03-23 12:44:26 |
Gerry Boland |
unity8 (Ubuntu): status |
Triaged |
Invalid |
|
2017-03-23 13:09:50 |
Michał Sawicz |
canonical-devices-system-image: assignee |
Michał Sawicz (saviq) |
Stephen M. Webb (bregma) |
|
2017-03-23 13:28:54 |
Stephen M. Webb |
mir (Ubuntu): assignee |
|
Andreas Pokorny (andreas-pokorny) |
|
2017-03-24 01:49:32 |
Daniel van Vugt |
bug task added |
|
mir |
|
2017-03-24 01:52:18 |
Daniel van Vugt |
mir: assignee |
|
Andreas Pokorny (andreas-pokorny) |
|
2017-03-24 01:52:22 |
Daniel van Vugt |
mir: importance |
Undecided |
High |
|
2017-03-24 01:52:25 |
Daniel van Vugt |
mir (Ubuntu): importance |
Undecided |
High |
|
2017-03-24 01:52:35 |
Daniel van Vugt |
tags |
amd64 apport-bug third-party-packages zesty |
amd64 apport-bug performance third-party-packages zesty |
|
2017-03-24 14:41:42 |
Andreas Pokorny |
description |
Steps:
* log in to unity8
* Ctrl+Alt+F* to a different vt, or log in to a different user session
* go back to the unity8 vt
Expected:
* session is locked, but working
Current:
* unity8 starts spinning for a time proportional to the period it was inactive
* if it was inactive long enough, it doesn't seem to recover at all
It seems it's "catching up" in some way, maybe with input, maybe frames.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555]
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Mar 23 11:36:39 2017
InstallationDate: Installed on 2016-05-06 (320 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago) |
Steps:
* log in to unity8
* Ctrl+Alt+F* to a different vt, or log in to a different user session
* go back to the unity8 vt
Expected:
* session is locked, but working
Current:
* unity8 starts spinning for a time proportional to the period it was inactive
* if it was inactive long enough, it doesn't seem to recover at all
It seems it's "catching up" in some way, maybe with input, maybe frames.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555]
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Mar 23 11:36:39 2017
InstallationDate: Installed on 2016-05-06 (320 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)
Causes:
The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events.
Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. |
|
2017-03-24 16:58:28 |
Launchpad Janitor |
branch linked |
|
lp:~andreas-pokorny/mir/fix-1675357 |
|
2017-03-25 08:37:08 |
Andreas Pokorny |
mir: status |
New |
In Progress |
|
2017-03-25 08:37:12 |
Andreas Pokorny |
mir: milestone |
|
1.0.0 |
|
2017-03-25 08:37:49 |
Andreas Pokorny |
nominated for series |
|
mir/0.26 |
|
2017-03-25 08:37:49 |
Andreas Pokorny |
bug task added |
|
mir/0.26 |
|
2017-03-25 08:37:58 |
Andreas Pokorny |
mir/0.26: assignee |
|
Andreas Pokorny (andreas-pokorny) |
|
2017-03-25 08:38:01 |
Andreas Pokorny |
mir/0.26: status |
New |
In Progress |
|
2017-03-25 08:38:28 |
Andreas Pokorny |
mir/0.26: milestone |
|
0.26.3 |
|
2017-03-25 08:38:34 |
Andreas Pokorny |
mir/0.26: importance |
Undecided |
High |
|
2017-03-25 08:40:42 |
Andreas Pokorny |
description |
Steps:
* log in to unity8
* Ctrl+Alt+F* to a different vt, or log in to a different user session
* go back to the unity8 vt
Expected:
* session is locked, but working
Current:
* unity8 starts spinning for a time proportional to the period it was inactive
* if it was inactive long enough, it doesn't seem to recover at all
It seems it's "catching up" in some way, maybe with input, maybe frames.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555]
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Mar 23 11:36:39 2017
InstallationDate: Installed on 2016-05-06 (320 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)
Causes:
The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events.
Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. |
Steps:
* log in to unity8
* Ctrl+Alt+F* to a different vt, or log in to a different user session
* go back to the unity8 vt
Expected:
* session is locked, but working
Current:
* unity8 starts spinning for a time proportional to the period it was inactive
* if it was inactive long enough, it doesn't seem to recover at all
It seems it's "catching up" in some way, maybe with input, maybe frames.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555]
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Mar 23 11:36:39 2017
InstallationDate: Installed on 2016-05-06 (320 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)
Causes:
The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events.
Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely.
This applies to all currently pressed buttons. I.e. you can open an edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to switch to another VT. On return 'w' will be repeated indefinitely. |
|
2017-03-27 06:57:49 |
Launchpad Janitor |
branch linked |
|
lp:mir/0.26 |
|
2017-03-27 06:58:06 |
Andreas Pokorny |
mir/0.26: status |
In Progress |
Fix Committed |
|
2017-03-27 07:06:19 |
Mir CI Bot |
mir: status |
In Progress |
Fix Committed |
|
2017-03-27 07:13:25 |
Andreas Pokorny |
qtmir (Ubuntu): status |
New |
Invalid |
|
2017-03-27 07:13:28 |
Andreas Pokorny |
mir (Ubuntu): status |
New |
Invalid |
|
2017-03-27 07:13:36 |
Andreas Pokorny |
mir (Ubuntu): status |
Invalid |
New |
|
2017-03-27 07:31:04 |
Daniel van Vugt |
canonical-devices-system-image: status |
Triaged |
Fix Committed |
|
2017-03-27 12:41:30 |
Stephen M. Webb |
canonical-devices-system-image: status |
Fix Committed |
In Progress |
|
2017-03-30 04:05:49 |
Daniel van Vugt |
mir (Ubuntu): status |
New |
Triaged |
|
2017-04-04 02:28:44 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683 |
|
2017-04-25 10:38:48 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-zesty-2735 |
|
2017-04-25 10:41:26 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736 |
|
2017-05-17 10:35:28 |
Timo Aaltonen |
nominated for series |
|
Ubuntu Xenial |
|
2017-05-17 10:35:28 |
Timo Aaltonen |
bug task added |
|
mir (Ubuntu Xenial) |
|
2017-05-17 10:35:28 |
Timo Aaltonen |
bug task added |
|
unity8 (Ubuntu Xenial) |
|
2017-05-17 10:35:28 |
Timo Aaltonen |
bug task added |
|
qtmir (Ubuntu Xenial) |
|
2017-05-17 10:35:47 |
Timo Aaltonen |
qtmir (Ubuntu Xenial): status |
New |
Invalid |
|
2017-05-17 10:35:53 |
Timo Aaltonen |
unity8 (Ubuntu Xenial): status |
New |
Invalid |
|
2017-05-17 10:43:26 |
Timo Aaltonen |
mir (Ubuntu Xenial): status |
New |
Fix Committed |
|
2017-05-17 10:43:28 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2017-05-17 10:43:32 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
2017-05-17 10:43:35 |
Timo Aaltonen |
tags |
amd64 apport-bug performance third-party-packages zesty |
amd64 apport-bug performance third-party-packages verification-needed zesty |
|
2017-05-17 21:28:43 |
Albert Astals Cid |
removed subscriber Albert Astals Cid |
|
|
|
2017-05-18 09:04:52 |
Alan Griffiths |
tags |
amd64 apport-bug performance third-party-packages verification-needed zesty |
amd64 apport-bug performance third-party-packages verification-done zesty |
|
2017-05-26 10:48:13 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-artful-2778 |
|
2017-05-28 13:18:03 |
Launchpad Janitor |
mir (Ubuntu): status |
Triaged |
Fix Released |
|
2017-05-29 03:20:38 |
Daniel van Vugt |
mir/0.26: status |
Fix Committed |
Fix Released |
|
2017-06-05 11:02:25 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1 |
|
2017-06-05 11:05:22 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-zesty-2791 |
|
2017-06-05 13:46:31 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783 |
|
2017-06-07 07:48:40 |
Chris Halse Rogers |
tags |
amd64 apport-bug performance third-party-packages verification-done zesty |
amd64 apport-bug performance third-party-packages zesty |
|
2017-06-07 07:48:42 |
Chris Halse Rogers |
tags |
amd64 apport-bug performance third-party-packages zesty |
amd64 apport-bug performance third-party-packages verification-needed zesty |
|
2017-06-07 07:51:02 |
Chris Halse Rogers |
mir (Ubuntu Yakkety): status |
New |
Fix Committed |
|
2017-06-07 09:46:58 |
Chris Halse Rogers |
mir (Ubuntu Zesty): status |
New |
Fix Committed |
|
2017-06-07 15:45:11 |
Michał Sawicz |
tags |
amd64 apport-bug performance third-party-packages verification-needed zesty |
amd64 apport-bug performance third-party-packages verification-done zesty |
|
2017-06-08 09:43:53 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-artful-2806 |
|
2017-06-09 16:28:35 |
Łukasz Zemczak |
tags |
amd64 apport-bug performance third-party-packages verification-done zesty |
amd64 apport-bug performance third-party-packages verification-done-xenial verification-done-yakkety verification-done-zesty zesty |
|
2017-06-15 13:55:23 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/mir/mir-ubuntu-zesty-2818 |
|
2017-06-15 14:15:24 |
Andy Whitcroft |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2017-06-15 14:16:11 |
Launchpad Janitor |
mir (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
2017-06-15 14:16:33 |
Launchpad Janitor |
mir (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
2017-06-15 14:25:31 |
Launchpad Janitor |
mir (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
2017-07-11 04:15:15 |
Daniel van Vugt |
mir: status |
Fix Committed |
Fix Released |
|