Bug 369638 - Incompatibility between addressbook entries Kontact 5.1.3 and 5.3.0
Summary: Incompatibility between addressbook entries Kontact 5.1.3 and 5.3.0
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: contacts (show other bugs)
Version: 5.1.3
Platform: Mint (Ubuntu based) Linux
: NOR critical
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-02 13:21 UTC by Frank
Modified: 2022-11-23 05:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank 2016-10-02 13:21:19 UTC
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.
Comment 1 Frank 2016-10-02 13:26:31 UTC
Forgot to mention:

I can import some of the over 200 entries. Only a subset causes the program to crash. I compared the "offending" and the working entries and could not find any obvious reasons. E.g. some entries using special accent characters work, some without crash.
Comment 2 Justin Zobel 2022-10-24 00:46:51 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-08 05:11:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-11-23 05:17:31 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!