Version: unspecified (using KDE 4.7.2) OS: Linux A contact copied to the clipboard is of type text/directory, which is unknown even to KDE. If I paste my contact data to a mail message, my recipients say WTF? It is really annoying how KDE does not enable me to efficiently communicate with other people. Reproducible: Always Steps to Reproduce: 1. Tell KAddressBook to copy the selected contact to the clipboard. 2. Tell KMail to paste into Composer. 3. Tell KMail to open the attachment. Actual Results: 2. text/directory 3. opens in KWrite Expected Results: 3. An offer to import the pasted contact into the address book. OS: Linux (x86_64) release 3.1.0-1.2-desktop Compiler: gcc ___ Workaround: 4. Tell KWrite to save the attachment as .vcard. 5. Tell Kontact to attach the .vcard file. This workaround does *not* work when the recipient uses KDE because KDE does not send VCards to KAddressBook. It opens them in KWrite, which does not make much sense if the VCard contains a photo. So in this case, the recipient also needs a workaround: 6. Tell KAddressBook to import the VCard.
After performing these steps, the contact became inaccessible in KAddressBook. It is grey in the contact list and nothing happens when I click on it.
(In reply to comment #1) > After performing these steps, the contact became inaccessible in KAddressBook. > It is grey in the contact list and nothing happens when I click on it. Actually, something happens: all actions get dispatched to the previous contact in the list.
I confirm it.
Still the case using KDE 4.8 - both the problem after copying, and the issue with wrong mimetype in kmail. The mimetype of the attached contact should be text/vcard, which can be displayed in a meaningful way (although kmails viewer fails showing the image).
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.
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.