Bug 165595

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
In my installation I am running.
evolution-2.2.3-1.fc4
evolution-data-server-1.2.3-2.fc4

This is a test server for a production SOE dekstop environment with real non technical end users running LTSP and FreeNX Terminal Services FC4

When you check the Edit Preferences

Version-Release number of selected component (if applicable):
evolution-2.2.3-1.fc4

How reproducible:
Always

Steps to Reproduce:
1. Start Evolution from the Launchmail icon on the Control Panel
2. Setup an LDAP address book (in my test case the user has write access to the LDAP store)
3. Goto Edit Preferences then Autocompletion and switch the checkbox on next to the addressbook you have created  (you can leave personal checked or uncheck it --> same result either way
4. Click close to clear the dialog
5. in the main window click the New button to create a new email message 
6. Start typing a name that you have verified is in your LDAP address book
(You can verify names are in your LDAP address book by clicking on Contacts and doing a search) --> you can also find them manually by clicking on the To button


Actual Results:  The Name does not auto resolve
if you try this with the personal address book for the same card (ie drag and drop a card that didn't work from you ldap store into your personal address book, make sure Autocompletion is checked for Personal, you will find that autocompletion works when you start typing a few charachters for an address book card (any email address that is in a card)

Expected Results:  Evolution should have started querying the LDAP server and tried to resolve the rest of the name real time autocompleting it   I have noticed that Queries are rather slow hitting OpenLDAP (which is on the same machine as my evolution) ie Dell GX270 / P4HT 3.0GHZ 1MBL2Cache / 4GB RAM) So I left it for 20 seconds and it still didn't resolve.



Additional info:

I haven't been able to test this in the past cause we were waiting on resolution the problem Bug #165269  We now have a fix for this and this has allowed us to progress in our use of Evolution Groupware components.