Merge lp:~mterry/unity8/shutdown-dialog-on-resume into lp:unity8
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Michael Terry | ||||
Approved revision: | 2009 | ||||
Merged at revision: | 2035 | ||||
Proposed branch: | lp:~mterry/unity8/shutdown-dialog-on-resume | ||||
Merge into: | lp:unity8 | ||||
Diff against target: |
179 lines (+51/-36) 5 files modified
plugins/Utils/windowkeysfilter.cpp (+15/-1) plugins/Utils/windowkeysfilter.h (+7/-0) qml/Components/PhysicalKeysMapper.qml (+16/-23) qml/Shell.qml (+2/-2) tests/qmltests/Components/tst_PhysicalKeysMapper.qml (+11/-10) |
||||
To merge this branch: | bzr merge lp:~mterry/unity8/shutdown-dialog-on-resume | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Needs Fixing | |
Albert Astals Cid (community) | Approve | ||
Michael Zanetti (community) | Needs Information | ||
Review via email: mp+275240@code.launchpad.net |
Commit message
Avoid showing the shutdown dialog when turning on the screen if your device is under heavy load.
Specifically, we actually watch the timestamp of input events as they come in to determine how long it's been. This means that if for whatever reason, processing of events get delayed, we don't misinterpret user input.
To test this, try running the following command and then turning the screen on and off again:
sudo cpulimit -l 1 -c 1 -p `ps ax | grep dbus-daemon | head -n 1 | awk '{print $1;}'`
Without this branch, you'll notice that at some point, you see the shutdown dialog in error. Because unity8 couldn't keep up with events and thought 2s passed between power-pressed and power-released events.
But if we watch the timestamps, we can avoid that particular fate.
Description of the change
* Are there any related MPs required for this MP to build/function as expected? Please list.
https:/
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
NA
* If you changed the UI, has there been a design review?
NA
FAILED: Continuous integration, rev:2005 jenkins. qa.ubuntu. com/job/ unity8- ci/6507/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 4754 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- wily-touch/ 889 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- vivid/1219 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- wily/535 jenkins. qa.ubuntu. com/job/ unity8- vivid-amd64- ci/1114 jenkins. qa.ubuntu. com/job/ unity8- vivid-i386- ci/1115 jenkins. qa.ubuntu. com/job/ unity8- wily-amd64- ci/746 jenkins. qa.ubuntu. com/job/ unity8- wily-i386- ci/747 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 3837 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 4751 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 4751/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 24444 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- wily-mako/ 526 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- wily-armhf/ 889 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- wily-armhf/ 889/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 24443
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/6507/ rebuild
http://