The original report for the browser was closed some time ago so I
suggest we need a new bug.
Per comment #27 this may be a new behavior with the new repowered in
ota13. (I added lp:1630986)
Per comment #25 I think this is actually functioning as intended, if an
app sets display on and is an active app we honor it. What is missing
IMO is any indication that this is the state of the display. Also would
be nice to add display on to the app permissions controlled via
settings.(lp:1630989)
** No longer affects: qtmir (Ubuntu)
** No longer affects: unity-system-compositor (Ubuntu)
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Released
** No longer affects: unity8 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1502145
Title:
Apps can keep screen lit permanently
Status in Canonical System Image:
Fix Released
Status in Oxide:
Fix Released
Status in Oxide 1.10 series:
Fix Released
Bug description:
rc-proposed, r140, krillin
There are times when it seems the display blanking policy stops
working and the display stays on until I press the power button.
Steps to reproduce:
* install and start Siete
* put it in background
Expected outcome:
* the display is switched off after a predetermined amount of time
Actual outcome:
* the display stays on forever
======
Now that apps can request the screen to stay on, they can do so
regardless of whether they're focused/visible or not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+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
