> I appears that you succesfully logged in via GDM the second time, but I
> assume that you weren't able to get in.
If you're talking about this:

Jun  8 13:30:12 heplw44 pam: gdm-password[7591]: 
pam_unix(gdm-password:auth): authentication failure; logname= uid=0 
euid=0 tty=:0 ruser= rhost=  user=ctooley
Jun  8 13:30:12 heplw44 pam: gdm-password[7591]: 
pam_sss(gdm-password:auth): authentication success; logname= uid=0 
euid=0 tty=:0 ruser= rhost= user=ctooley

The second time is sssd confirming my login credentials via LDAP - at 
least, that's what it should be doing - my nsswitch.conf uses "files 
sss" for users and groups.

I figured it would be something to do with

Jun  8 13:30:12 heplw44 polkitd(authority=local): Unregistered 
Authentication Agent for session /org/freedesktop/ConsoleKit/Session32 
(system bus name :1.199, object path 
/org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)

But I haven't a clue if this would be something that's supposed to fail 
gracefully or not.

> When that happens to one of my users, the first thing I look at is their
> home area.
> Make sure it exists, make sure it's read/write for that user on login,
> and make sure the file system for their home area isn't full (overquota
> or something like that.)

All permissions are correct for this user, I even made sure that the 
quota was OK, there doesn't appear to be any problems there.

-Chris