Bug 176124
Summary: | [RHEL4] LDAP addressbook authentication setting changes require a restart to take effect | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Suzanne Hillman <shillman> |
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED WONTFIX | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 4.0 | CC: | nalin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-03 16:29:31 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: |
Description
Suzanne Hillman
2005-12-19 17:19:31 UTC
Putting as specific to x86_64 for now (viper, specifically), until it gets tested on an i386. Suzanne, we appear to have several servers scattered around our network. I try to keep http://intranet.corp.redhat.com/ic/intranet/NetworkClientConfiguration.html reasonably up to date, and (in case it helps) have just updated the list of directory servers noted there. Nalin - thanks. I asked others, and the one I was testing with appeared to work for other people. So it's not the server. However, I shall copy that link for later knowledge! Can you give me access to the client machine where this is failing? Please can you: (i) give more detail in step 3. (ii) the result of running: rpm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" evolution evolution-data-server openldap I can successfully connect to that server using RHEL4 U2 on x86_64 on one of my test boxes, by doing a search in the Contacts component. This is with U2: evolution-2.0.2-22.x86_64 evolution-data-server-1.0.2-9.x86_64 openldap-2.2.13-3.i386 openldap-2.2.13-3.x86_64 Latest for U3 is evolution-2.0.2-25.x86_64 (e-d-s hasn't upgraded) openldap has bumped from 2.2.13-3 to 2.2.13-4 in a post-U2 errata Tried upgrading just evolution; addressbook search within Contacts component still works; this is with: evolution-2.0.2-25.x86_64 evolution-data-server-1.0.2-9.x86_64 openldap-2.2.13-3.i386 openldap-2.2.13-3.x86_64 (doing an "evolution --force-shutdown" after each upgrade, to ensure we don't have a stale e-d-s process in memory) Tried upgrading openldap, and it still works, this is with: evolution-2.0.2-25.x86_64 evolution-data-server-1.0.2-9.x86_64 openldap-2.2.13-4.i386 openldap-2.2.13-4.x86_64 I guess I really just need access to that machine to try to debug what the problem is and its extent. BTW, if you run evolution --force-shutdown then manually start /usr/libexec/evolution-data-server-1.0 at a terminal, then start evolution, you should see extensive LDAP debug information. You had "Use Secure Password: Always"; should be "Never". I changed it to "Never" and it continued to fail; I needed to restart the evolution-data-server process before it would work (it now works on that machine). So the bug is that you need to restart e-d-s before that change takes effect. (I believe that this is not a regression) Ah. I thought I had tried restarting with both Always and with Never, but noted! Should I leave this open to stand in for the bug relating to needing to restart, or not? As for regression, I thought that I did not have to restart evo in order to get it to work, but I'm not positive. For now, removing regression label. If you have to restart a user-level application for a change in settings to take effect, then that should be clearly labelled in the UI (or else it's a bug). The only case I can think of is in evolution-connector, where it explicitly warns you to restart. So I think this bug should be renamed to "LDAP addressbook authentication setting changes require a restart to take effect" I just reproduced this on a RHEL4 U2-ish box: evolution-2.0.2-22 evolution-data-server-1.0.2-9.fix169497.1 so I'm fairly sure this is not a regression. (and this was on a VMware i386 instance) Problem still affects rawhide: evolution-2.5.2-1 evolution-data-server-1.5.2-1 Looks like a duplicate of this upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=261783 Evolution 2.0.2 is only being updated for security issues. Closing as WONTFIX. |