Bug 274007

Summary:	Kaddressbook does not print out error messages when creating a new LDAP address book fails.
Product:	[Applications] kaddressbook	Reporter:	Stephan Diestelhorst <stephan.diestelhorst>
Component:	ldap search	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	tokoe
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Stephan Diestelhorst 2011-05-24 06:11:47 UTC

Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

Have tried to add the company address book to Kaddressbook through LDAP. Kaddressbook either loops forever, or is just silent, and does not show the new address book.

Looking into ~/.xsession-errors reveals for example

akonadi_kabc_resource_8(13556): Loading error:  "Der LDAP-Server gibt folgende Fehlermeldung aus: Size limit exceeded 
Weitere Informationen: 
Die LDAP-Adresse ist: ldap://foo" 

or 

akonadi_kabc_resource_6(13537): Loading error:  "Der LDAP-Server gibt folgende Fehlermeldung aus: Operations error 
Weitere Informationen: 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed o
n the connection., data 0, vece
Die LDAP-Adresse ist: ldap://foo" 

Two things are a nuisance here:
1) the error message is not conveyed to the user
2) the settings for the new address book are lost, making incremental fixes to the LDAP data impossible

I will report the size limit exceeded issue as a separate bug.

Thanks for looking into this!

Reproducible: Always

Steps to Reproduce:
* open kaddressbook
* create new address book
* standard resource
* LDAP
* enter not quite the right LDAP settings

Actual Results:  
Error messages are not sent to the user.
The user is not notified of a problem.
The entered server data etc. is lost.

Expected Results:  
* dialog with the LDAP server's error message
* be back at the setup pane, with settings still filled in

Comment 1 Denis Kurz 2016-09-24 20:52:24 UTC

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.

Comment 2 Denis Kurz 2017-01-07 21:55:08 UTC

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.