Bug 299704

Summary: Importing of contacts into an address book results in the replacement of custom field names with alphanumeric strings
Product: [Applications] kaddressbook Reporter: K. A. Sayeed <sayeed.ka>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: auxsvr, montel, tokoe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description K. A. Sayeed 2012-05-09 20:15:31 UTC 
1. Contacts were imported into the current address book (in the latest version of KDE Kontact) from another address book using the ".vcf" format.
2. On examination of the imported contacts, it was found that the alphabetic custom field names were replaced by alphanumeric strings. For example, the field name "CREATION TIME:" was replaced by "2c80efe1-5e2f-4702-a1a9-17b9fc980395".

Reproducible: Sometimes

Steps to Reproduce:
1. Import the contacts from an existing address book  using the "Import Vcard" menu item into an address book in the current address book.
2. Select a contact entry and open it in edit mode.
3. Examine the custom field names in the contact entry. 
3.
Actual Results:  
The alphabetic custom field names were replaced by alphanumeric strings.

Expected Results:  
The alphabetic custom field names should remain the same.

1. The computer system was using Kubuntu 12.04.
2. The KDE Kontact was installed by the Kubuntu 12.04 installer.
3. The addresses were imported from KDE Kontact running on Ubuntu 11.10.
Comment 1 Laurent Montel 2012-06-29 07:48:24 UTC 
I confirm it
Comment 2 Denis Kurz 2016-09-24 20:52:47 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 3 Denis Kurz 2017-01-07 21:27:51 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.