Bug 1277831

Summary: Settings->Privacy->Screen Lock: OFF does not necessarily allow other screen savers
Product: [Fedora] Fedora Reporter: Norman Goldstein <normvcr>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 22CC: fmuellner, jmccann, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 20:15:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Norman Goldstein 2015-11-04 08:11:01 UTC
Description of problem:

Settings->Privacy->Screen Lock: OFF does not necessarily allow other screen savers to take control of the screen.

Version-Release number of selected component (if applicable):

GNOME 3.16

How reproducible:

Always

Steps to Reproduce:
1. Set Settings->Privacy->Screen Lock: OFF
2. Install xscreensaver
3.

Actual results:

When xscreensaver is configured to kick in after 11 minutes, the GNOME lock screen takes over, instead.

When xscreensaver is configured to kick in after 1 minute, xscreensaver takes over (as expected)

Expected results:
xscreensaver should always take over after its configured wait time has elapsed.


Additional info:

The command
gnome-session-inhibit --inhibit-only
does allow xscreensaver to always take over (as expected)

Comment 1 Yaakov Selkowitz 2015-11-04 08:16:55 UTC
Recent versions of GNOME do not use gnome-screensaver for screen locking; reassigning.

Comment 2 Fedora End Of Life 2016-07-19 20:15:20 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.