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 632536 - fails to add a contact list to a LDAP server
fails to add a contact list to a LDAP server
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Contacts
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-10-19 10:36 UTC by jwarnier
Modified: 2011-02-03 02:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jwarnier 2010-10-19 10:36:39 UTC 
Evolution cannot add any contact list to a (Open)LDAP server.
Adding the same contact list to a local addressbook works nicely.

While I guess this could be related with the schemas used on the LDAP server, I think the error message in Evolution is at least shorter than it could, and existing documentation does not match reality.

I wonder if anybody really ever got a LDAP addressbook fully working (all features) since Evolution 2.x.
I know for sure it worked in 1.0 or 1.2, as we (Stan Pinte, working for BeezNest) even submitted a patch at that time to fix some tags ignored.

Please note this has already been submitted earlier in Ubuntu's Launchpad:
https://bugs.launchpad.net/evolution/+bug/595037

Regards
Comment 1 Milan Crha 2010-11-03 13:41:26 UTC 
Thanks for a bug report. What is the error it says? When you run evolution-data-server on another console with LDAP_DEBUG=1 exported, will it print more detailed information on the console in time of trying to create a new contact list on the LDAP server?
Comment 2 Akhil Laddha 2010-12-17 05:57:02 UTC 
jwarnier, ping, can you please collect the information asked in comment#1 and update the bug.
Comment 3 Fabio Durán Verdugo 2011-02-03 02:46:44 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!