Bug 128762 (screensaverissue)
Summary: | lock screen after can be less than bkank after or cycle after | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | ashok pappu <a.pappu> |
Component: | xscreensaver | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | a.pappu, jwz, mattdm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | screensaver-properties-capplet invalid settings | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-05-11 21:30:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
ashok pappu
2004-07-29 05:02:47 UTC
That's not how it works. From the manual: Lock Screen When this is checked, the screen will be locked when it activates. Lock Screen After This controls the length of the ''grace period'' between when the screensaver activates, and when the screen becomes locked. For example, if this is 5 minutes, and Blank After is 10 minutes, then after 10 minutes, the screen would blank. If there was user activity at 12 minutes, no password would be required to un-blank the screen. But, if there was user activity at 15 minutes or later (that is, Lock Screen After minutes after activation) then a pass- word would be required. The default is 0, meaning that if locking is enabled, then a password will be required as soon as the screen blanks. Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. Hi, This bug is being closed because it has been in the NEEDINFO state for a long time now. Feel free to reopen the bug report if the problem still happens for you and you can provide any information that was requested. |