touch-packages team mailing list archive

[kevin gunn <kevin.gunn@xxxxxxxxxxxxx>]

removing duplicate marker.
bug 1426115 is about the screen timing out faster in the case where the screen is turned on by a system event such as a notification vs. a user touch/interaction

** This bug is no longer a duplicate of bug 1426115
   Screen timeout for events needs to be a shorter duration than the standard inactivity timeout

** Also affects: unity-system-compositor (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: unity-system-compositor
   Importance: Undecided
       Status: New

** Tags added: pm-fail

-- 
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/1472262

Title:
  Screen lock and lock screen timeouts are conflated

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  1. Set Security & Privacy -> Lock phone to "After 10 minutes"
  2. Lock phone (or wait 10 minutes for it to lock).
  3. Receive a text.

  Expected behaviour: screen turns off very soon after to conserve
  battery (I expect between 5 and 60 seconds).

  Actual behaviour: screen remains on for 10 minutes, draining battery.

  Even worse, if I set the lock to "Never" then after receiving a text
  the screen will never turn off. In this case I expect to take
  responsibility for turning the screen off when I am done using it, but
  I expect the phone not to turn the screen back on when I am not around
  and receive a notification unless the phone does time it out in that
  case.

  I think the screen lock timeout should be completely separate from the
  lock screen timeout. I would like to set 10 minutes or never for the
  screen lock timeout, but I still want the lock screen to time out and
  turn the display off after a few seconds.

  I found bug 1420493 which is in a related area but doesn't refer to
  the lock screen timeout itself. My failure case is a use case about
  battery drain, rather than needing to repeatedly re-enter the
  passcode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1472262/+subscriptions