Hide Forgot
Description of problem: User confusion caused by incorrect enablement state of checkboxes in gnome-screensaver-preferences for "Lock screen when screensaver is active" "Activate screensaver when computer is idle" when a gconf mandatory profile exists for these settings. That makes a user think they can e.g. change the setting, while the checkbox has no effect in reality and should be disabled (as opposed to Bug 759395, which allowed a user to really change a mandatory setting). My observations with particular mandatory keys (when set alone, not in combinations): idle_activation_enabled = true: "Activate screensaver when computer is idle" checkbox is enabled - incorrect, should be disabled "Lock screen when screensaver is active" checkbox is enabled - correct idle_activation_enabled = false: "Activate screensaver when computer is idle" checkbox is enabled - incorrect, should be disabled "Lock screen when screensaver is active" checkbox is disabled - correct lock_enabled = true or false: "Activate screensaver when computer is idle" checkbox is disabled - incorrect, should be enabled "Lock screen when screensaver is active" checkbox is disabled - correct Version-Release number of selected component (if applicable): gnome-screensaver-2.28.3-24.el6_4.1.x86_64 How reproducible: always Steps to Reproduce: 1. Set one of the keys like above, e.g. gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type boolean --set /apps/gnome-screensaver/lock_enabled true 2. Re-log to your account 3. Compare with what's in gnome-screensaver-preferences Actual results: Checkbox enablement does not match gconf. Expected results: Checkbox enablement should match gconf.
To avoid confusion please note that by "enabled" or "disabled" checkboxes in Comment 0 I meant grayed or not grayed out (ie. available for a user to change their state). This bug has nothing to do with the checkboxes' states (checked/unchecked).
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/