GNOME Bugzilla – Bug 361668
Broken autocomplete with an LDAP evoluton address book
Last modified: 2009-01-19 19:23:27 UTC
Please describe the problem: When an LDAP address book is defined is evolution, with autocomplete activated, nautilus-sendto does'nt work well. The evolution nautilus-sendto plugin first get all contacts of all adress books, but this is taking a huge amount of time when the number of contacts on the LDAP server is high. In practice I have to wait tens of seconds before seeing the nautilus-sendto dialog. I believe maybe nautilus-sendto should use the same autocomplete strategy as the new mail dialog in evolution, which work fine with an LDAP based address book, even with a huge number of contacts. Steps to reproduce: 1. configure an LDAP address book in evolution, with a LDAP server having lots of contacts (say thousands) 2. configure autocomplete for this address book 3. start nautilus sendto Actual results: I have to wait a very long time before seeing the nautilus-sendto dialog. Expected results: Does this happen every time? Yes. Other information:
Does autocompletion work well with your LDAP setup in evolution? I have heard many reports about problems there too..
Evolution autocomplete with LDAP works quite nicely with Evo 2.8 (at least on my setup, YMMV). This is not wihtout any issue I would say (occasional crashes), but given that the current nautilus-sendto autocomplete is useless with a significantly big LDAP addressbook, I would say that the best would be to reuse Evolution autocomplete, and fix it where it is needed. Alternatively (in the meantime ?) autocomplete in nautilus-sendto for LDAP addressbooks could be disabled (so that we can activate autocomplete in Evo wihtout nautilus-sendto taking minutes to startup) ? (=> maybe status can be set to "NEW" ?) Thanks.
We should use the contact entry from contact-lookup-applet instead, as is done in gnome-phone-manager.
We do that now in trunk, could you please test?
*** Bug 516539 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!