wondering now, could this just be a duplicate of bug 1531167 ?
e.g. maybe the low battery is compliant, but we have a case of proximtiy-screen
freakout?
** Changed in: unity-system-compositor (Ubuntu)
Status: Opinion => New
** Changed in: unity-system-compositor (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: unity-system-compositor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1566028
Title:
low battery notification does not honor proximity sensor
Status in Canonical System Image:
Confirmed
Status in unity-system-compositor package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
per our "display blanking spec" we want all notifications to activate
the proximity sensor & be obedient to it. This includes any dialogs
that are initiated without user input.
(from Pat) One example is I experienced the low battery notification
which turned on the screen, ignoring proximity, and allowing
subsequent touch events that lead to a locked device. I later
reproduced this by covering the sensor completely and seeing that in
fact the screen is always turned on.
it's worth noting that all other notifications appear to obey the
proximity sensor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566028/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
