After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 326000 - Evolution hangs on LDAP Access associated with address completion
Evolution hangs on LDAP Access associated with address completion
Status: RESOLVED DUPLICATE of bug 330161
Product: evolution
Classification: Applications
Component: Contacts
2.4.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-06 17:30 UTC by Cameron Kellough
Modified: 2006-02-08 00:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Cameron Kellough 2006-01-06 17:30:09 UTC 
Please describe the problem:
When typing an address into the To window of a new message with autocompletion
tunred on and an LDAP server not on my local network, Evolution's user interface
froze completely.

Steps to reproduce:
1. Type address into to window with autocompletion
2. watch for hang
3. 


Actual results:
The user interface becomes completely unresponsive.
evolution --forceshutdown won't get rid of the evolution windows open
kill must be used.

Expected results:
either autocompletion or no autocompletion but no program hang.

Does this happen every time?
No,  I cannot repeat it.  

Other information:
Comment 1 André Klapper 2006-01-07 16:18:21 UTC 
it is "evolution --force-shutdown", perhaps that's the reason it did not work
Comment 2 parthasarathi susarla 2006-01-31 07:00:52 UTC 
Thanks for the bug report. Without a stack trace from the crash/hang it's very hard to determine what caused it.
Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.


Also i think this is more of an Addressbook issue. So changing the component
Comment 3 Cameron Kellough 2006-02-08 00:44:47 UTC 

*** This bug has been marked as a duplicate of 330161 ***