Lucid session idle timeout is too short

Bug #523299 reported by David Siegel
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
GNOME Screensaver
Invalid
Undecided
Unassigned
One Hundred Papercuts
Triaged
Low
Unassigned
gnome-screensaver (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

In Lucid, the session idle timeout is set to 5 minutes--the shortest possible timeout allowed by the Screensaver preferences--by default. This value should be set to 30 minutes instead to lower the frequency with which the screensaver activates, and the screen locks itself, when user is attending to the computer but not touching the keyboard or mouse.

Changed in hundredpapercuts:
status: New → Confirmed
description: updated
summary: - Lucid screen saver idle timeout is too short
+ Lucid session idle timeout is too short
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

I disagree with this. I do not see why it should be more than the bare minimum, for two reasons:
- Security. Screen locking is good.
- Power management: turning off the screen is good. Furthermore, the gnome-power-manager timeouts kind-of depend on the gnome-screensaver timeout, I think.

Revision history for this message
David Siegel (djsiegel-deactivatedaccount) wrote :

By your argument, why don't we lock the screen after 1 minute? How about 30 seconds?

- Security: I am not suggesting we get rid of locking here, I am saying that 5 minutes is too short. My screen locks all of the time when I'm simply sitting in front of my computer, not interacting with it.
- Turning the screen off is sufficient to save power, the lock doesn't contribute to this. I only want to push the lock timeout back, I still think it's fine to shut the screen off or active the screensaver sooner. It's a separate issue if this is currently not easy to implement, I am reporting a bug in the user experience.

Revision history for this message
Vish (vish) wrote :

We can probably change this as a distro setting.

Marking bug as triaged.

Changed in gnome-screensaver (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Changed in gnome-screensaver:
status: New → Invalid
Changed in hundredpapercuts:
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

I'm thinking enterprise setting/coffee break scenario here. 5-10 minutes is reasonable, 30 minutes is an insanely long amount of time to leave a work computer unattended and wide open to any passerby to fiddle with. The default setting should be closer to a secure setting. Users who don't need security (ie: home users) can disable automatic screen locking or prolong the timeout.

This is similar in spirit to a no open ports/insecure services default policy, or a default policy of asking a password to log-in (ubuntu does offer you the option to autologin though).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.