https://bugs.kde.org/show_bug.cgi?id=369638
Bug ID: 369638 Summary: Incompatibility between addressbook entries Kontact 5.1.3 and 5.3.0 Product: kontact Version: 5.1.3 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: contacts Assignee: to...@kde.org Reporter: fhe...@inbox.lv CC: kdepim-bugs@kde.org I just installed Linux Mint 18 KDE Version (which is shipping Kontact 5.1.3) and tried to load my CardDAV addressbook, which I am using without Problems on gentoo/Kontact-5.3.0. And unfortunately this crashes the whole application repeatedly upon opening of the Kontact tab. It does not seem to be connected to the CarDDAV module but the actual parsing of the address fields. Reproducible: Always Steps to Reproduce: 1. Import or load Addressbook from Kontakt-5.3.0 either via CardDAV or from vcard/ldif export 2. 3. Actual Results: Some of the addressbook entries that work under Kontact-5.3.0 crash this 5.1.3 version. Repeatedly and so bad that the contact module cannot be opened and the offending entries cannot be deleted. Expected Results: It should parse the addressbook field entries in a sane way and report a problem if something does not fit and not crash the program. Also the entries should be compatible over minor version changes. I took quite so time to narrow down the error. First I thought the CardDAV exchange mechanism was faulty, but that was not the case. CalDAV works and the problem could be reproduced by manually importing the data from 5.3.0 into 5.1.3 default local addressbook as well. Then the import crashes! This bug is unfortunately so severe, that is corrupts in some way the akonadi database and prevents opening the contact module at all. Therefore the only fix I could find is akonadictl stop manually delete whole database and config under .local/.config akonadictl start This makes the contact module accessible again, but it will of course again crash upon importing an offending entry. I also thought the pictures I added to my addressbook would be the problem, but als an ldif export crashed the program. So it seems to be the parsing of the text field entries that has a serious problem. As this causes segfaults on the main program I consider it also a potential serious security issue. -- You are receiving this mail because: You are on the CC list for the bug.