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 236011 - LDAP access seem to be a bit unstable
LDAP access seem to be a bit unstable
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Contacts
pre-1.5 (obsolete)
Other other
: Normal normal
: Future
Assigned To: evolution-addressbook-maintainers
Evolution QA team
evolution[ldap]
Depends on:
Blocks: 327508 327510
 
 
Reported: 2002-12-20 22:42 UTC by Marcin Kasperski
Modified: 2012-01-30 13:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marcin Kasperski 2002-12-20 22:42:08 UTC
{ Unfortunately I am unable to describe the very nature of the problem,
  please treat it as a suggestion to review the LDAP access behaviour }

While I was trying to access some LDAP service (in fact, the one which
I am just starting to run) it repeatably happened to me that evolution
reported errors like 'can not access this address book' or did not asked
for the password although it should or asked for the password but when
I entered it claimed it was wrong (and I am 100% sure I used the correct
password, I even tried it succesfully with other LDAP client against the
same server at the same time). In all those cases slapd did not reported any
access from the client (and I run it with debug logging enabled).

It can matter that I was restarting the LDAP server (and I restarted
evolution after each slapd restart), I was reconfiguring the evolution
using different access method, I was changing access rules of LDAP server etc.
Comment 1 Sushma Rai 2005-08-24 08:11:42 UTC
Can you upgrade evolution and try this?
Also try starting evolution-data-server in a seperate
console, so that we can see if there are any log related messages.
Comment 2 André Klapper 2006-02-18 10:22:02 UTC
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!
Also, this version of Evolution is obsolete, as sushma already said.
Comment 3 Marcin Kasperski 2006-06-08 16:51:01 UTC
I have not been using evolution for about 3 years, so it is hard to comment on the issue. Nevertheless, I would recommend making the simple test before closing the bug (hmm, adding it to some release test suite if there is any):
- configure evolution to access some ldap server,
- make some search,
- restart this server,
- make next search
Comment 4 Sushma Rai 2006-06-29 08:33:35 UTC
Devashish, Poornima, 
Can we test this scenario?
Comment 5 André Klapper 2006-06-29 14:18:55 UTC
removing old target milestone.
sush: CC them, otherwise you wont get an answer.
Comment 6 Alexander Hunziker 2007-06-12 13:57:48 UTC
I'm afraid I cannot add anything very precise to this bug, except that also for me, LDAP on Evolution just "doesn't work". I somehow get the feeling that the LDAP implementation in Evolution is simply broken. Parameters easily accepted by Thunderbird wont give any search results in Evolution, neither an error message, just nothing.
Comment 7 Milan Crha 2008-07-10 15:20:59 UTC
srag, see comment #3 please

Alexander, I would like to look at it, but I can connect to my ldap server, the only thing is to search for some term, it doesn't show "all" contacts. But I see above you search for contacts already.
Comment 8 Alexander Hunziker 2008-07-10 18:43:40 UTC
I'm now successfully searching the University LDAP server using evolution. It is sometimes unstable, especially when using LDAP for address autocompletion, but in general it works.
Comment 9 Milan Crha 2008-07-11 06:39:18 UTC
Hi, thanks for quick answer. In which way is it unstable?
Comment 10 James Andrewartha 2008-09-16 20:33:27 UTC
Evolution doesn't handle server restarts that well - the first operation after the server restarts will fail. So:
- search (works)
- restart ldap server
- search (fails)
- search (works)
or
- search (works)
- restart ldap server
- edit contact and save (fails)
- search (works)
Comment 11 André Klapper 2012-01-30 13:59:01 UTC
The scope of this bug report is extremely vague and basically unfixable (and adding new comments with different new problems is another sign for that) so I am closing this ticket.

If you have specific problems with Evolution 3.2 or 3.0 and LDAP access, please file a separate new bug report. Thanks!