On 09/16/2011 02:09 PM, Colin Guthrie wrote: > Hi, > > OK, so there seem to be a couple bugs related to this still outstanding. > > I've been testing things today and I rebooted into kdm and logged into > KDE and all was well. > > So I'd like to try and work out who is still having problems and if I > can help debug. > > As I understand it, Guillaume is still having issues with systemd+gdm, > but no problems with kdm in that setup. > > So can someone summarise things here so I can attempt to reproduce? > > For reference, I'm up to date as of a couple hours ago. > > rpm -V kdm gdm pam > > Only some inconsequential changes are left, although my system-auth file > is a bit different. > > Here is what I have: > > > #%PAM-1.0 > > auth required pam_env.so > auth sufficient pam_tcb.so shadow nullok prefix=$2a$ count=8 > auth required pam_deny.so > > account sufficient pam_tcb.so shadow > account required pam_deny.so > > password required pam_cracklib.so try_first_pass retry=3 > minlen=4 dcredit=0 ucredit=0 > password sufficient pam_tcb.so use_authtok shadow write_to=shadow > nullok prefix=$2a$ count=8 > password required pam_deny.so > > session optional pam_keyinit.so revoke > session required pam_limits.so > session [success=1 default=ignore] pam_succeed_if.so service in > crond quiet use_uid > -session optional pam_systemd.so > session required pam_tcb.so > > > And here is the diff from the .rpmnew file there: > --- system-auth.rpmnew 2011-08-27 13:06:24.000000000 +0100 > +++ system-auth 2011-08-27 13:08:41.049923085 +0100 > @@ -4,9 +4,10 @@ > auth sufficient pam_tcb.so shadow nullok prefix=$2a$ count=8 > auth required pam_deny.so > > -account required pam_tcb.so shadow > +account sufficient pam_tcb.so shadow > +account required pam_deny.so > > -password required pam_cracklib.so try_first_pass retry=3 > +password required pam_cracklib.so try_first_pass retry=3 > minlen=4 dcredit=0 ucredit=0 > password sufficient pam_tcb.so use_authtok shadow write_to=shadow > nullok prefix=$2a$ count=8 > password required pam_deny.so > > > > > Cheers > > Col > > >
I'm still having a problem where systemd never finishes to a point of loading tty's. I'm using KDM and I turned off plymouth to see if that was the issue. KDM does start and the system, as far as I can tell, is working okay, but I can't log into any tty console. The systems been up for 20+ hours now and tty1 is still showing: Started LSB: run cron daemon. Scott
