Package: libnss-ldap Version: 238-1 Followup-For: Bug #302296
hi! i encountered the same problems. have been using the pam-ldap, libnss-ldap for a year now without problems until that named update last week. i am certain this is not connected to any window-manager. the sessions cannot be created properly, but login itself gets authenticated as one can see from the logs. not that i like it. on the other hand, all the info that goes through libnss-ldap is not really a secret within my company. so changing uri ldaps://whatever.host.we.want/ to uri ldap://localhost/ and of course having an ldap locally solves the problem completely for me. (please also check: bug #306546). i would say it is not the remote/local host that "fixes" the situation - rather it is the little "s" after "ldap" :-) the reason why ssh-logins are not affected by this is (i guess) that i set "UsePrivilegeSeparation no" in the sshd_config like everybody else who wants to use ssh and ldap. and as far as i understand, this lets some process run as root and so the assert(`mutex->__data.__owner == 0') will eval to true ... (might all be bullshit as i am a "zero" at C) please let me know if i can provide any additional information. regs and thank u for your effort, klaus -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages libnss-ldap depends on: ii debconf 1.4.30.13 Debian configuration management sy ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libkrb53 1.3.6-2 MIT Kerberos runtime libraries ii libldap2 2.1.30-3 OpenLDAP libraries -- debconf information: * libnss-ldap/dblogin: false * shared/ldapns/base-dn: dc=example,dc=net libnss-ldap/binddn: cn=proxyuser,dc=example,dc=net * libnss-ldap/override: false * shared/ldapns/ldap-server: 127.0.0.1 * libnss-ldap/confperm: false * shared/ldapns/ldap_version: 3 * libnss-ldap/nsswitch: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
