kabcdistlistupdater crash on kde startup

[P]

Binary package hint: kdepim

kabcdistlistupdater crash on kde startup
since updates of 2008 oct 16th

stack trace joined

[Michael-seiwert (michael-seiwert)]

Version: 1.8 (using KDE KDE 3.4.0)
Installed from: Unspecified Linux
Compiler: gcc-Version 3.3.1 (SuSE Linux)
OS: Linux

KMail crashes if I have ldapkio resource enabled. I can reproduce this crash if start up kmail, navigate through random imap folders and displaying random messages. After several operations it crashes. It seems not to crash if I stay in inbox. It doesn't seem to matter if the "From" is in ldap or not. Attached are the backtrace and valgrind trace.

[Michael-seiwert (michael-seiwert)]

Created attachment 10593
valgrind trace

produced with:
valgrind --tool=addrcheck --num-callers=50 kmail --nofork 2>&1 | tee log

[Michael-seiwert (michael-seiwert)]

Created attachment 10594
kmail backtrace

kdepim is compiled with --enable-debug=full

[David Faure (faure)]

Very good valgrind log, thanks.

==14774== by 0x39945849: KABC::ResourceLDAPKIO::enter_loop() (in /opt/kdehead/lib/libkabc_ldapkio.so.1.0.0)
WAHHH. Using enter_loop is a very very bad idea, in case anyone still had doubts about that.

If ldapkio's loading is async, kabc should load it async, instead of having to
emulate sync from async using the very dangerous enter_loop.
Tobias, is this possible?

[Harald Sitter (apachelogger)]

Is this in any way reproducible? If so, please install kdepim-dbg and get a new trace, otherwise we should close this bug report.
The current trace is totally unusable, as indicated by the amount of (no debugging symbols found) messages, in theory a good backtrace should have no such messages at all. In order to archive this, the appropriate debugging symbols need to be installed (i.e. $PACKAGE-dbg)

[Wouter Horré (wouterh)]

I have the same crashes since the recent updates to KDE 3.5.10.

KCrash backtrace with kdepim-dbg installed is attached.

[Wouter Horré (wouterh)]

In attachment a backtrace produced with the instructions on http://wiki.ubuntu.com/Backtrace.

[Harald Sitter (apachelogger)]

Confirmed due to backtraces.

[Andreas Wenning (andreas-wenning)]

Thanks for reporting.

Do you use LDAP or is your setup in any way different from the standard/filebased solution?

[Andreas Wenning (andreas-wenning)]

Just to be clear: It is of course your addressbook (kaddressbook in kmail/kdepim) that I am interested in.

[Wouter Horré (wouterh)]

I had a contact list in LDAP (with off-line use configured) that was no longer reachable. I have deleted this resource and now I can't reproduce the crash anymore.

[Andreas Wenning (andreas-wenning)]

@Wouter
Thanks for testing that.

Is it possible to re-enable off-line use for that resource, and does the resource then work? Does the crash then start to appear again?

[Wouter Horré (wouterh)]

I had actually deleted the whole addressbook resource (as I no langer used it). I have now created a dummy LDAP addressbook for an addressbook on a non-reacheable server and the crash reappeared. I have not enabled off-line use for this addressbook.

You should be able to reproduce the crash by adding the following resource to ~/.kde/share/config/kresources/contact/stdrc:
[Resource_aDChoggJK6]
LdapAnonymous=true
LdapAttributes=city,l,commonName,cn,description,description,facsimileTelephoneNumber,facsimileTelephoneNumber,familyName,sn,formattedName,displayName,givenName,givenName,jpegPhoto,jpegPhoto,mail,mail,mailAlias,,mobile,mobile,objectClass,inetOrgPerson,organization,o,pager,pager,phoneNumber,homePhone,postalcode,postalCode,state,st,street,street,telephoneNumber,telephoneNumber,title,title,uid,uid
LdapAutoCache=true
LdapBindDN=
LdapCachePolicy=0
LdapDn=cn=addressbook,dc=wouter,dc=horre,dc=be
LdapFilter=
LdapHost=localhost
LdapMech=DIGEST-MD5
LdapPassword=
LdapPort=389
LdapRDNPrefix=0
LdapRealm=
LdapSASL=false
LdapSSL=false
LdapSizeLimit=0
LdapSubTree=true
LdapTLS=false
LdapTimeLimit=0
LdapUser=
LdapVer=3
ResourceIdentifier=aDChoggJK6
ResourceIsActive=true
ResourceIsReadOnly=false
ResourceName=ldapkio address book
ResourceType=ldapkio

[P (p92)]

Hey

I use local address books and an ldap address book which is reachable when the crash occurs.

I use the following resource for ldap :

LdapAnonymous=false
LdapAttributes=city,l,commonName,cn,description,description,facsimileTelephoneNumber,facsimileTelephoneNumber,familyName,sn,formattedName,displayName,givenName,givenName,jpegPhoto,jpegPhoto,mail,mail,mailAlias,,mobile,mobile,objectClass,inetOrgPerson,organization,o,pager,pager,phoneNumber,homePhone,postalcode,postalCode,state,st,street,street,telephoneNumber,telephoneNumber,title,title,uid,uid
LdapAutoCache=true
LdapBindDN=
LdapCachePolicy=1
LdapDn=ou=shared_addressbook,ou=horde,dc=hostname,dc=fr
LdapFilter=
LdapHost=ldap.hostname.fr
LdapMech=DIGEST-MD5
LdapPassword=toto
LdapPort=636
LdapRDNPrefix=0
LdapRealm=
LdapSASL=false
LdapSSL=true
LdapSizeLimit=0
LdapSubTree=true
LdapTLS=false
LdapTimeLimit=0
LdapUser=uid=secuid,ou=DSA,dc=hostname,dc=fr
LdapVer=3
ResourceIdentifier=2DRrL74KXL
ResourceIsActive=true
ResourceIsReadOnly=false
ResourceName=myldap
ResourceType=ldapkio

[Andreas Wenning (andreas-wenning)]

Crashes upon calling the constructor of StdAddressBook exactly per the spec. in the .h file:
KABC::AddressBook *ab = KABC::StdAddressBook::self();

Reassigning to kdelibs instead.

[Jonathan Thomas (echidnaman)]

KDE 3.5.x is unmaintained by KDE, and since Hardy support ends next month, this bug won't be fixed. Security updates will continue in to next month, providing security issues pop up, but normal bugs most likely won't be fixed.

[Søren Holm (sgh)]

It this allso what happenens when kmail crashes when entering a recipient in a new email?

[thx1011 (thx1011)]

Hi!

I Have the same problem. Crashing of Kmail when adding a recipient to the TO: or CC: or BCC: fields, and during the LDAP lookup.

My Kmail version is 1.12.1 on KDE 4.3.1, and the previous version had'nt this problem....

[Søren Holm (sgh)]

For me it is fixed in 4.3.4

[Søren Holm (sgh)]

Please close this bug.

[Myriam Schweingruber (myriam)]

Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding