2015-09-14 18:55:53 |
Oliver Grawert |
bug |
|
|
added bug |
2015-10-19 21:15:04 |
Pat McGowan |
canonical-devices-system-image: importance |
Undecided |
Medium |
|
2015-10-19 21:15:04 |
Pat McGowan |
canonical-devices-system-image: status |
New |
Confirmed |
|
2015-10-19 21:15:04 |
Pat McGowan |
canonical-devices-system-image: milestone |
|
backlog |
|
2015-10-19 21:15:04 |
Pat McGowan |
canonical-devices-system-image: assignee |
|
Yuan-Chen Cheng (ycheng-twn) |
|
2016-06-14 15:56:41 |
Pat McGowan |
tags |
|
display-control |
|
2016-06-14 15:57:53 |
Pat McGowan |
bug task added |
|
arale |
|
2016-06-14 16:04:13 |
Pat McGowan |
description |
when locking the screen on arale the home button stays fully active (when the screen times out as well) ... this is massively annoying, i often press that button by accident after locking the screen and when waking up the device it opens on the first scope instead of the app that was open when i locked it (or when it timed out) |
when locking the screen on arale the home button stays fully active (when the screen times out as well) ... this is massively annoying, i often press that button by accident after locking the screen and when waking up the device it opens on the first scope instead of the app that was open when i locked it (or when it timed out)
--------------
It seems to be inconsistent in that it is not always enabled even immediately after hitting power. Other times touching it much later wakes the device, so it seems to be an input state we get into.
Just seen on rc-prorposed 348 |
|
2016-06-28 11:22:57 |
Pat McGowan |
bug task added |
|
repowerd (Ubuntu) |
|
2016-06-28 11:23:18 |
Pat McGowan |
canonical-devices-system-image: assignee |
Yuan-Chen Cheng (ycheng-twn) |
kevin gunn (kgunn72) |
|
2016-06-28 14:01:19 |
Launchpad Janitor |
repowerd (Ubuntu): status |
New |
Confirmed |
|
2016-07-27 20:13:05 |
Jonas |
bug |
|
|
added subscriber Jonas |