GNOME Bugzilla – Bug 671608
Can not see LDAP contacts
Last modified: 2012-11-28 13:27:30 UTC
Hello, Since 3.2.2 I can't access LDAP contact data. In a new mail the completion does not work anymore. The LDAP server is working and I can use it through utilities like Jxplorer. First LDAP server (master) slapd -VV @(#) $OpenLDAP: slapd 2.4.23 (Jun 16 2011 02:53:39) $ buildd@murphy:/build/buildd-openldap_2.4.23-7.2-i386-Y1mwvF/openldap-2.4.23/debian/build/servers/slapd Second LDAP server (slave) slapd -VV @(#) $OpenLDAP: slapd (Jan 16 2012 18:57:39) $ julien@radis:/tmp/openldap-2.4.28/debian/build/servers/slapd The servers are working on a non standard port (489) and no connections on that port are visible on the servers. Regards JPP
you are not able to auto complete contacts from ldap address book, right ? can you see contacts when you go to contacts and click on ldap address book ?
Also see http://projects.gnome.org/evolution/bugs.shtml how to debug with LDAP_DEBUG.
Hello, I can't see contacts in the contact screen and no connection exists between LDAP server and Evolution. Will try to use the LDAP_DEBUG method and I will send results. Regards JPP
Hello, I try to use the LDAP_DEBUG tricks : export LDAP_DEBUG=1 cd /usr/lib/evolution ./e-addressbook-factory gives some output : e-data-server-Message: adding type `EBookBackendWebdavFactory' e-data-server-Message: adding type `EBookBackendGoogleFactory' e-data-server-Message: adding type `EBookBackendLDAPFactory' e-data-server-Message: adding type `EBookBackendFileFactory' e-data-server-Message: adding type `EBookBackendVCFFactory' Server is up and running... Then I launch Evolution and get new messages : libebookbackend-Message: supported server control: 1.3.6.1.4.1.4203.1.9.1.1 libebookbackend-Message: supported server control: 2.16.840.1.113730.3.4.18 libebookbackend-Message: supported server control: 2.16.840.1.113730.3.4.2 libebookbackend-Message: supported server control: 1.3.6.1.4.1.4203.1.10.1 libebookbackend-Message: supported server control: 1.2.840.113556.1.4.319 libebookbackend-Message: supported server control: 1.2.826.0.1.3344810.2.3 libebookbackend-Message: supported server control: 1.3.6.1.1.13.2 libebookbackend-Message: supported server control: 1.3.6.1.1.13.1 libebookbackend-Message: supported server control: 1.3.6.1.1.12 libebookbackend-Message: supported server extension: 1.3.6.1.4.1.4203.1.11.1 libebookbackend-Message: supported server extension: 1.3.6.1.4.1.4203.1.11.3 libebookbackend-Message: supported server extension: 1.3.6.1.1.8 libebookbackend-Message: supported SASL mechanism: NTLM libebookbackend-Message: supported SASL mechanism: DIGEST-MD5 libebookbackend-Message: supported SASL mechanism: CRAM-MD5 e_book_backend_ldap_connect ... success e_book_backend_ldap_connect took 0.009 seconds It seems to work ... and when I go to the "contact" screen the responses are OK. If I send a mail the completion works and contacts are OK, I don't join the screen output as it lists only response to the LDAP queries. Even if I stop (Ctrl+C) the factory the LDAP server are "usable". Will try more after some time and a reboot ... Regards JP P
I am seeing the same thing - if I start evolution LDAP doesn't seem to work - however if I then stop evolution and restart evolution-addressbook-factory (I am running Evo 3.4.3 on F17) with LDAP_DEBUG=1 then LDAP works and continues to work until I restart my machine - at which point I need to restart e-addressbook-factory with LDAP_DEBUG again to get it to work.. I think that perhaps there is some race condition where if debugging is enabled it slows down evolution-addressbook-factory enough to avoid it (and then perhaps cache some result like the password or something) whereas when debugging is not enabled it returns too quickly and this is missed??
Thanks for a bug report. I do no think it's about debugging being on or off, it's rather about bug #681815, where the restart of addressbook factory is enough to get it working again. *** This bug has been marked as a duplicate of bug 681815 ***