Red Hat Bugzilla – Bug 441560
Should mark pam files as %config
Last modified: 2014-06-03 08:37:46 EDT
Description of problem:
gnome-screensaver makes display unusable since update to
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start gnome session
2. Wait for screensaver to start
Moving mouse produces blank screen with only large cursor visible. Unlock screen
never displayed. Typing password anyway has no effect. Can not return display to
normal w/o killing gnome-screensaver.
Unlock screen displayed, display returns to normal after entering password.
My settings are
Screensaver theme: Blank
Regard the computer as idle after: 1 minute (for testing)
Activate screensaver when computer is idle: YES
Lock screen when screensaver is active: YES
Thanks for the report. Unfortunately, I'm unable to reproduce this.
Can you please provide us with some additional information?
First, kill off gnome-screensaver:
pkill -f gnome-screensaver
Then run with debugging enabled and redirect this to a file:
gnome-screensaver --no-daemon --debug > gs.log 2>&1
Then reproduce the problem and attach the gs.log here.
Created attachment 301714 [details]
Debug output from gnome-screensaver
Looks like you may be using a remote directory service (nis, nis+, ldap, etc),
I think will occur is you are not connected to the network and are not running
nscd. If you ensure that you are connected to the same network as your
directory does this still occur?
You are on the right path. I use ldap for account information, kerberos for
authentication. For reasons that aren't worth explaining, the gnome-screensaver
pam file is modified, rather than system-auth.
gnome-screensaver-2.16.1-5.el5_1.1 replaced the pam file and gnome-screensaver
could not get account information.
Two things for you to consider whether this is a bug or not:
1. Packages usually do not replace modified config files, instead create a
2. Should gnome-screensaver fail in this way when it can't obtain account
information? Seems inelegant.
Thanks for the help!
Great! So, you are probably right. We should mark the pam file as %config so
it isn't replaced. Thanks for testing this.
You're also right that we should display a message when this occurs. But that
isn't something we could do in that security errata. I've created the following
bug for that:
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).