Lock screen isn't cat-friendly (no input timemout)

Bug #1292695 reported by Adam Conrad on 2014-03-14
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
High
Unassigned

Bug Description

gnome-screensaver's lock screen has an input timeout, so that if you, say, lock your screen and have a cat walk across your keyboard in the middle of the night, after N seconds (don't recall how long it is) of no input, it gives up and blanks the screen again. The new unity lock screen appears to be missing this feature, as I woke up this morning to a password box filled with dots and a screen that had been on all night.

It looks like maybe there had been a failed attempt to address this use-case, as once one clears the password field and logs in, a second or two later, the screen re-locks and you need to log in again.

Stephen M. Webb (bregma) on 2014-03-16
Changed in unity (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Andrea Azzarone (andyrock)
Changed in unity:
importance: Undecided → High
Stephen M. Webb (bregma) on 2014-03-25
Changed in unity:
milestone: none → 7.2.0
status: New → Triaged
Adam Conrad (adconrad) wrote :

Wait. Is unity 7.2 targetted for trusty, or did this milestone target basically just say "leaving screens on all night is an acceptable behaviour for an LTS"?

david6 (andrew-dowden) wrote :

This is NOT a duplicate of: Bug #1292041 (since closed)

This relates to screen not blanking (and screen turning off) after a mouse or keyboard event, when in screen-locked state.

This is annoying and is still present in latest, fully patched, Ubuntu 16.04.1 LTS.

This bus is present in 16.04.

Single monitor
System Settings, Brightness and Lock, Turn screen off when inactive for: 10 minutes.

dpms activates after 10 minutes of inactivity

activate Lock from menu or Ctrl+Alt+L
dpms never activates

Is this still a problem for anyone.

I know that on my 16.10 installation it works as expected. 16.04.1 LTS fully updated should have roughly the same version of Unity.

david6 (andrew-dowden) wrote :

I have NOT yet tested this on clean install of 16.10 ..

But NO, it is still present on 16.04.1 LTS, fully updated.

Andrea Azzarone (azzar1) on 2017-10-13
no longer affects: unity
Changed in unity (Ubuntu):
assignee: Andrea Azzarone (azzar1) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers