Bug 179048

Summary: kontact: Editing data in vcard-files changes filename
Product: [Applications] kontact Reporter: Stefan Neufeind <kde>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: rdieter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Stefan Neufeind 2008-12-29 14:31:19 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

Had one contact in a separate file, was using "dir address book" in kontact to
access the data. Upon modifying the data, the name changed from "123" to some
cryptic string (unique identifier?). Also the revision-tag that was placed in
the original file was removed.
The original files have been created by syncing a mobile phone (using
msynctool) to a vcard30-storageformat into a directory.

anonymised form of the original vcard:
BEGIN:VCARD
VERSION:3.0
ADR;TYPE=HOME:;;abc;abc;;12345;abc
ADR;TYPE=WORK:;;abc;abc;;12345;abc
EMAIL;TYPE=INTERNET:abc@example.com
N:Paul;Mueller;;;
ORG:abc;
REV:20070731T124117Z
TEL;TYPE=WORK:+99 (123) 456789
TEL;TYPE=CELL:+99 (234) 567890
URL:http://www.example.com/
END:VCARD

and of the resulting vcard after editing/saving the entry in kontact:
BEGIN:VCARD
ADR;TYPE=HOME:;;abc;abc;;12345;abc
ADR;TYPE=WORK:;;abc;abc;;12345;abc
CLASS:PUBLIC
EMAIL:abc@example.com
FN:Paul Mueller
N:Paul;Mueller;;;
ORG:abc
REV:2008-12-28T14:53:20Z
TEL;TYPE=WORK:+99 (123) 456789
TEL;TYPE=CELL:+99 (234) 567890
UID:2WuGkU8Odu
URL:http://www.example.com/
VERSION:3.0
END:VCARD


PS: also tracked at https://bugzilla.redhat.com/show_bug.cgi?id=478346
Comment 1 Denis Kurz 2016-09-24 19:27:10 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 kontact (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 22:05: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.