** Changed in: mir (Ubuntu)
Status: New => Triaged
--
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/1675357
Title:
Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while)
Status in Canonical System Image:
In Progress
Status in Mir:
Fix Committed
Status in Mir 0.26 series:
Fix Committed
Status in mir package in Ubuntu:
Triaged
Status in qtmir package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu:
Invalid
Bug 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.
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+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
