Bug 112297
| Summary: | Evolution still tries to lookup directory servers in disconnected mode | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Nick Strugnell <nstrug> |
| Component: | evolution | Assignee: | Dave Malcolm <dmalcolm> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-05-18 01:35:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Looks like this is in upstream Bugzilla as http://bugzilla.ximian.com/show_bug.cgi?id=35377 |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922 Description of problem: If an LDAP server is configured as a directory server, evolution tries to use it to autocomplete email addresses in offline mode. This causes a delay which hangs the entire UI until the lookup times out. Looking at the Offline Folders tab in Settings, it appears that Evolution automatically assumes that anything under 'Other Contacts' is an offline-available folder. LDAP contacts folders should be marked as unavailable in offline mode as IMAP folders are. Version-Release number of selected component (if applicable): evolution-1.4.5-1 How reproducible: Always Steps to Reproduce: 1.Configure an LDAP server in evolution 2. Take machine off network 3. Go into offline mode (by clicking the connection icon in lower LH corner) 4. Create a new e-mail and start typing a name in the 'To:' field Actual Results: UI hangs while LDAP connection is attempted and eventually times out Expected Results: Name should be either resolved from local contacts folder or unresolved Additional info: Could try running a local cacheing LDAP server on laptop and pointing at that as workaround