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 683855 - After upgrade to 3.4 (from 3.2) ldap does not authenticate
After upgrade to 3.4 (from 3.2) ldap does not authenticate
Status: RESOLVED DUPLICATE of bug 681815
Product: evolution
Classification: Applications
Component: Contacts
3.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-09-12 08:57 UTC by Mehmet Giritli
Modified: 2012-09-14 09:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mehmet Giritli 2012-09-12 08:57:56 UTC 
I didn't have any problems with ldap problem or authentication to this date until I upgraded to gnome 3.4. My ldap server complains that:

Sep 12 09:36:26 gollum slapd[22979]: conn=1023 op=1 SEARCH RESULT tag=101 err=13 nentries=0 text=confidentiality required

i.e., evolution does not login with the DN I provided.

I tried to delete the addressbook and add a new one but I get the same result. BTW, I expected it to ask for my password after I added the new account and it didn't (I did try to connect with the new account and got the same error). Sounds like a symptom to me.

There is no changes for ldap server. It is the same server running before.
Comment 1 Milan Crha 2012-09-13 11:31:16 UTC 
Thanks for a bug report. What is the exact Evolution version, please? (Help->About) Does it help if you choose menu File->Forget passwords, then close evolution and other evolution processes (ps ax | grep evolution), and then run evolution from scratch?
Comment 2 Mehmet Giritli 2012-09-13 12:10:22 UTC 
Hey, thanks for that. It solved my problem. I don't know what exactly happened but it worked. The version was 3.4.4
Comment 3 Mehmet Giritli 2012-09-13 17:45:52 UTC 
Nope, it came back again. I did the same procedure you describe, it worked after that but on the next run it is spitting the same error message with insufficient access...
Comment 4 Mehmet Giritli 2012-09-13 18:00:49 UTC 
I just discovered that unchecking birthdays & anniversaries thingy fixes the problem. But I kinda want to have this feature...
Comment 5 Milan Crha 2012-09-14 06:45:29 UTC 
Thanks for the update. This sounds just like bug #681815. Could you enable the Birthday & Anniversaries calendar and try this:
a) close evolution
b) close/kill other evolution processes (ps ax | grep evolution)
c) run evolution

The restart of evolution-addressbook-factory usually helps.
Comment 6 Mehmet Giritli 2012-09-14 09:46:44 UTC 
Okay did more testing now and I now think that bdays option is actually not relevant.

It seems to work after every fresh start (i.e., after killing old instances) except the first time with gnome login. So, yes it is exactly like that bug. Marking as a dupe.

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