From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051215 Fedora/1.7.12-3

Description of problem:
After starting yum to update my system via a root gnome-terminal, I could not unlock xscreensaver using my known password. I could however change to a virtual terminal and login to a terminal. After logging in to a terminal, I could kill xscreensaver as a regular user. After switching back to the console, I found that typing text in my root gnome-terminal would fail. I could drag the window of te terminal, highlight text but not type anything within the terminal.
I then pressed ctl-alt-delete to exit the session of X. When the session restarted gdm could not authenticate user.
I therefore logged into another virtual terminal as root. I then ran 'setenforce 0'.
After that, I changed to the console and killed X again with ctl-alt-backspace. Authentication still failed. with the error message repeating when I clicked OK and ctl-alt-backspace respawning gdm, I switched to a regular user account and started X using 'startx -- :8'
The startx login was succesful and the system was in a usable state with the new X session with 'setenforce 0' still set.
After closing down critical tasks, I rebooted the system and appended 'autorelabel' to the grub loader. The system now seems to be acting normally.
Switching to to my virtual terminal for

Version-Release number of selected component (if applicable):
selinux-policy-targeted-2.1.6-4 xscreensaver-base-4.22-21 pam-0.99.2.1-1

How reproducible:
Didn't try

Steps to Reproduce:

1. start yum to update system via script that updates what does not have dep problems. Let yum run unattended.
2. lock screensaver and go to work
3. get home (over 8 hours), screensavers cycling
4. Press key, password box appears.
5. Type password, xscreensaver login fails
6. Switch to virtual terminal, log in as regular user
7 killall -9 xscreensaver
8. switch back to (X) console
9. enter open gnome-termnal by clicking with mouse
10. try typing text, no echo from terminal
11 . ctl-alt-backspace to restart X
12. gdm authentication fails, click on dialog box
13. log into another virtual terminal and issue 'setenforce 0'
14: switch to console and ctl-alt-backspace gdm again
15. get error dialog stating authentication, click on dialog box OK button, which repeatadly respawns on OK click
16. switch to normal user and run startx -- :8 to get a GUI session active
  

Actual Results:  Whenever I typed in my password to unlock xscreensaver, authentication would fail.
When xscreensaver was killed, a GUI was present on screen 0, but no text could be typed in the open root gnome-terminal.
Launching from a normal user an X session on screen 8 via startx -- :8 worked successfully. gdm was still present with error dialog box on display 0.
rebooting and relabeling system seemed to correct the problem.

Expected Results:  A system updated with packages that met dep requirements.
The ability to unlock xscreensaver via the login box w/ flame.
See normal activity on the computer.

Additional info:

The secure log seems to have details related to the authentication problem. I will submit logs with seemingly related failure logging.