After an in-place online update, which otherwise looks good, I've run into an issue with gdm and LDAP. First behavior I ran into, conflict with nss-pam-ldapd and nss_ldap I chose nss-pam-ldapd, figured out that I needed to start nslcd.service and I can now log into console sessions. That said, I didn't really test console login with nss_ldap. GDM login no longer errors out quickly with a bad password note, it now looks to be doing something, waits a while, and then returns to the greeter. Looking through the logs I see this: gdm-password]: pam_unix(gdm-password:auth): authentication failure; (PID removed). I've looked through the /etc/pam.d files, and nothing seems obvious. I've tried pam-config --add --ldap, which, prior to adding nss-pam-ldapd showed 2 missing libraries. Yast config for LDAP shows the config, but applying any change trips an error about package install failure (no indication of what packages that I can see in logs or anywere else). This is what led me to switch to nss-pam-ldapd, but the Yast LDAP-client config still behaves the same way. I'm not sure how to debug and/or resolve, any suggestions? -- __________________________________________________________________________ Josef Fortier Systems Administrator fortier@augsburg.edu Phone: 612-330-1479 __________________________________________________________________________ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org