Bug 328449 - kaddressbook copy and paste contacts is broken badly
Summary: kaddressbook copy and paste contacts is broken badly
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: VCard dir resource (show other bugs)
Version: 4.11
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-05 12:19 UTC by Hans-Peter Jansen
Modified: 2017-01-07 22:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Jansen 2013-12-05 12:19:11 UTC
A usual operation with contacts is to copy a contact and adjust the copied
contact, e.g. adjust name and email address of a college of some business
contact.

Doing so with current kde4 addressbook is badly broken in this respect. 

I'm using several contact sources, the one in question is a vcard folder,
shared with KDE3 desktops, but it also happens with folders managed by akonadi,
e.g. ~/.local/share/contacts/, as well as ~/.kde/share/apps/kabc/std.vcf, hence
I believe, it's a general kaddressbook (or akonadi) issue.


Reproducible: Always

Steps to Reproduce:
1. Select an address, and copy it via context menu
2. paste address to this addressbook via context menu
Actual Results:  
The contact appears twice for a short time, but if you edit one to adjust name
and email address, the original contact is _replaced_ by the new one. This is
not, what copying contacts is about. 

Expected Results:  
Both contacts should be available steadily.
Comment 1 Denis Kurz 2016-09-24 20:41:18 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:43:26 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.