Hello, I'm experiencing similar gdm login problems in combination with libnss-ldap. Some playing around with strace/gdb revealed the following:
1. gdm starts 2. libnss-ldap opens a (tls/ssl) connection to the LDAP server. This connection is not closed after use. It is kept open for future LDAP lookups. 3. gdm closes all open filedescriptor (using function gdm_close_all_descriptors defined in daemon/misc.c). This also closes the socket used for communicating with the LDAP server. 4. gdm opens a new connection to the X server. The filedescriptor of this connection is the same as the filedescriptor that was used for the LDAP server connection. 5. user enters username/password. 6. libnss-ldap attempt to contact the LDAP server again, unfortunately, the data gets send to the X-server instead. libnss-ldap does not know its socket was closed by gdm. 7. login fails. 8. gdm restarts. Perhaps it is possible to tell libnss-ldap not to keep its socket open, but IMHO, the real problems is gdm. I 'fixed' the problems by commenting out the entire implementation of gdm_close_all_descriptors. It seems to work, though I haven't checked for side-effects/security implications... Groetjes, Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
