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 273711 - ldap search does not return any results.
ldap search does not return any results.
Status: RESOLVED DUPLICATE of bug 274308
Product: evolution
Classification: Applications
Component: Contacts
2.2.x (obsolete)
Other All
: Normal blocker
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-03-15 13:19 UTC by Moussa Razzouki
Modified: 2005-04-06 10:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Moussa Razzouki 2005-03-15 13:19:48 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

Evolution does not work with our corporate ldap server. It connects
fine and can find "possible search bases" in the 'add server' dialog.
But when quering, not matter whitch fields it returns nothing.
The search completes instantly (read: I can see somthing flashing by
in the statusbar. But this is shown in a fraction of a second).
Further, after clearing the search a message is spawned saying:
"Unable to perform search-->This Query did not complete successfully"

The odd thing is that all other mailclients i've tried work perfectly.
I have this issue since version 2.0 and have had it also with the 
development releases i've tried - in the hope this would be solved.
I'am using Gnome and would really love to use evolution with our
corporate addressbook.

I'll paste "debugging" information under the addid. info section below.



Steps to reproduce the problem:
1. Add an ldap server in contacts and search for existing contacts.
2. 
3. 

Actual Results:

All ldap searches results are empty, while with other ldap
clients same searches result in found items.

Expected Results:

ldap search should return entries queried for.
How often does this happen? 

All the time.

Additional Information:

rel@entropy ~ $ evolution --force-shutdown
Shutting down evolution-alarm-notify (Evolution Calendar alarm notification
service)
rel@entropy ~ $
rel@entropy ~ $ killall evolution-data-server-1.2 ;
/usr/libexec/evolution-data-server-1.2
evolution-data-server-1.2(8676): Operation not permitted
evolution-data-server-1.2: no process killed
evolution-data-server-Message: Starting server
e-data-server-Message: adding type `EBookBackendFileFactory'
e-data-server-Message: adding type `EBookBackendVCFFactory'
e-data-server-Message: adding type `EBookBackendLDAPFactory'
e-data-server-Message: adding type `EBookBackendGroupwiseFactory'
e-data-server-Message: adding type `ECalBackendFileTodosFactory'
e-data-server-Message: adding type `ECalBackendFileEventsFactory'
e-data-server-Message: adding type `ECalBackendGroupwiseTodosFactory'
e-data-server-Message: adding type `ECalBackendGroupwiseEventsFactory'
e-data-server-Message: adding type `ECalBackendHttpTodosFactory'
e-data-server-Message: adding type `ECalBackendHttpEventsFactory'
e-data-server-Message: adding type `ECalBackendContactsEventsFactory'
e-data-server-Message: adding type `ECalBackendWeatherEventsFactory'
in server_log_handler
evolution-data-server-Message: Server up and running
impl_GNOME_Evolution_Addressbook_BookFactory_getBook
 + ldap://ldap.int.kn:389/o=Kuehne and Nagel??one
in server_log_handler
libebookbackend-Message: libldap vendor/version: OpenLDAP  2.00.130
in server_log_handler
libebookbackend-Message: library extensions present:
in server_log_handler
libebookbackend-Message: X_OPENLDAP
 => 0x8085cc0
impl_GNOME_Evolution_Addressbook_Book_open (0x8085cc0)
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.2
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.3
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.4
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.5
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.6
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.7
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.8
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.9
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.10
in server_log_handler
libebookbackend-Message: supported server control: 2.16.840.1.113531.18.2.11
in server_log_handler
libebookbackend-Message: supported SASL mechanism: EXTERNAL
cal = 0x8097b60
cal = 0x80c2a98
impl_GNOME_Evolution_Addressbook_BookFactory_getBook
 + file:///home/rel/.evolution/addressbook/local/system
 => 0x8081c68
impl_GNOME_Evolution_Addressbook_Book_open (0x8081c68)

(evolution-data-server:9067): libedata-book-WARNING **:
impl_GNOME_Evolution_Addressbook_Book_getBookView ((contains
"x-evolution-any-field"  ""))

e_data_book_respond_get_book_view
starting book view thread
starting initial population of book view
signalling parent thread
impl_GNOME_Evolution_Addressbook_BookFactory_getBook
 + file:///home/rel/.evolution/addressbook/local/1107179051.18920.0@entropy
returning from start_book_view
 => 0x80cc2f0
impl_GNOME_Evolution_Addressbook_Book_open (0x80cc2f0)

(evolution-data-server:9067): libedata-book-WARNING **:
impl_GNOME_Evolution_Addressbook_Book_getBookView ((contains
"x-evolution-any-field"  ""))

e_data_book_respond_get_book_view
starting book view thread
starting initial population of book view
signalling parent thread
returning from start_book_view
cal = 0x8090960
cal = 0x80b8e88
finished population of book view
finished population of book view

(evolution-data-server:9067): libedata-book-WARNING **:
impl_GNOME_Evolution_Addressbook_Book_getBookView ((beginswith "full_name"
 "moussa"))

e_data_book_respond_get_book_view
start_book_view (0x80b6228)
searching server using filter: (& (objectclass=person)
(|(cn=moussa*)(sn=moussa*)) ) (expecting max 100 results)
adding search_op (0x80b6228, 4)
looked up msgid 4, got op 0x8107070
ldap_search_handler (0x80b6228)
ldap_search_dtor (0x80b6228)
stop_book_view (0x80b6228)

(evolution-data-server:9067): libedata-book-WARNING **:
impl_GNOME_Evolution_Addressbook_Book_getBookView ((contains
"x-evolution-any-field"  "jan"))

e_data_book_respond_get_book_view
start_book_view (0x8091540)
searching server using filter: (& (objectclass=person)
(|(cn=*jan*)(sn=*jan*)(mail=*jan*)(primaryPhone=*jan*)(telephoneNumber=*jan*)(homePhone=*jan*)(mobile=*jan*)(carPhone=*jan*)(facsimileTelephoneNumber=*jan*)(homeFacsimileTelephoneNumber=*jan*)(otherPhone=*jan*)(otherFacsimileTelephoneNumber=*jan*)(internationaliSDNNumber=*jan*)(pager=*jan*)(radio=*jan*)(telex=*jan*)(assistantPhone=*jan*)(companyPhone=*jan*)(callbackPhone=*jan*)(tty=*jan*)(o=*jan*)(ou=*jan*)(roomNumber=*jan*)(title=*jan*)(businessRole=*jan*)(managerName=*jan*)(assistantName=*jan*)(postalAddress=*jan*)(homePostalAddress=*jan*)(otherPostalAddress=*jan*)(jpegPhoto=*jan*)(userCertificate=*jan*)(labeledURI=*jan*)(displayName=*jan*)(spouseName=*jan*)(note=*jan*)(anniversary=*jan*)(birthDate=*jan*)(mailer=*jan*)(fileAs=*jan*)(category=*jan*)(calCalURI=*jan*)(calFBURL=*jan*)(icsCalendar=*jan*))
) (expecting max 100 results)
adding search_op (0x8091540, 6)
looked up msgid 6, got op 0x80915a0
ldap_search_handler (0x8091540)
in server_log_handler

(evolution-data-server:9067): libebookbackend-WARNING **:
ldap_search_handler: 11 (Undefined attribute type), additional info: Bad
search filter
ldap_search_dtor (0x8091540)
Comment 1 Moussa Razzouki 2005-03-22 12:36:31 UTC
Some notes that may be helpfull:

I have searched with ldapsearch and I may know what the cause
may be.

In the evo "ldap server" properties for the configured server
I can set the "search scope" to "one" or "sub"; default is "one".
Now when setting this to "sub" and clicking oke, it will be 
resetted back to "one" again. No way to set it to "sub".

What has this todo with the bug? Well.. with ldapsearch when setting
the scope to base or one "-s one" or "-s base", the search returns
nothing. When not using the -s switch or using "-s sub" the search 
returns entries. So my logical conclusion is that evo doesn't let
me use sub and so I cannot use our ldap server with it.

-Moussa
Comment 2 Sivaiah 2005-03-29 18:47:30 UTC
(evolution-data-server:9067): libebookbackend-WARNING **:
ldap_search_handler: 11 (Undefined attribute type), additional info: Bad
search filter
ldap_search_dtor (0x8091540)


this seems to be important one , evo is receving bad search filter so
no search actaully happened, it seems there seems to be a mismatch
between schema on your ldap server and what ldap attributes evo is
using in search filter 
Comment 3 Nagappan Alagappan 2005-04-04 07:12:48 UTC
I tried with Novell eDirectory and ADS, it worked fine. Can you please
provide some more info ? (like: ldap server details...)
Comment 4 Moussa Razzouki 2005-04-05 08:25:15 UTC
It works now, with a workaround. What I did is change the 
"search scope" via gconf-editor (/apps/evolution/addressbook/source)
because evo wouldnt let me. Always falling back to the default 
value whitch is "one". I did this because ldapsearch fails
with scope "one" and succeeds with "sub" as I described above.

Nagappan:
All the info I know about the ldap-server is provided in the paste:
version: OpenLDAP  2.00.130??


-moussa


Comment 5 Sivaiah 2005-04-06 10:51:11 UTC
ok i see the problem of changes to seach socpe and search base not
getting saved. this is a dup of bug 274308  then

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