Version: unspecified (using KDE 4.6.2) OS: Linux It seems that my company's LDAP server has a limit smaller than the number of employees (> 1000). While setting the limit field in the query pane is fine, the server still sends an error if the number of results exceeds that limit. What the actual fix should be is using the simple paging extension as described in RFC 2696. With the command line tool ldapsearch the following parameters work: ldapsearch -LLL -h <server> -x -W -D <user> -b <base> "(objectClass=user)" cn objectClass -E pr=100 prints several results and then Press [size] Enter for the next {100|size} entries. Which returns the next 100 entries. With nromal limiting like this ldapsearch -LLL -h <server> -x -W -D <user> -b <base> "(objectClass=user)" cn objectClass -E pr=100 I get: Size limit exceeded (4) Together with bug 274007, this is quite annoying. Reproducible: Always Steps to Reproduce: Query an LDAP server that has more entries than either the configured or specified size limit. Actual Results: Kaddressbook does not create an address book due to the server error message. Expected Results: Kaddressbook should use the paging extension and query the huge address book page by page, as to not exceed the size limitation.
In kdepimlibs-4.6.3 there's paging control support. At least there's some code that talks about it and it works for me! Note that I had a similar looking problem when trying to connect to an LDAP server that was too old to support the paging option. So each attempt to talk to it would fail with size limit exceeded. Switching to a different ldap server 'fixed' it, but it would be useful if KDE could require the paging option. i.e. the equivalent in ldapsearch of: -E 'pr=10/noprompt' vs -E '!pr=10/noprompt' But that's a different bug....
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.