Bug 254872 - kaddressbook: adding contact via mouseclik in kmail leads to duplicate if already existing
Summary: kaddressbook: adding contact via mouseclik in kmail leads to duplicate if alr...
Status: RESOLVED FIXED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-21 15:04 UTC by Mathias
Modified: 2010-10-22 13:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias 2010-10-21 15:04:47 UTC 
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

If I right-click on an email address in kmail and choose "Add Address to Addressbook" it adds this contact to the addressbook regardless if it is already there, thus filling the addressbook with duplicates. In former versions (of the interface between kmail and kaddressbook or one of the two?) kmail warned me that the entry already exists and not has been added again.

Reproducible: Always

Steps to Reproduce:
right-click on an email address in kmail and choose "Add Address to Addressbook"

Actual Results:  
kmail/kaddressbook adds this address to the addressbook - also if it already exists 

Expected Results:  
kmail should warn me that the entry already exists and not has been added again

System: Gentoo 64bit, kernel 2.6.34-r11, kmail 1.13.5, kaddressbook 4.4.5
Comment 1 Tobias Koenig 2010-10-22 01:19:14 UTC 
Hej Mathias,

this bug is already fixed. Please make sure that you have Nepomuk running and configured properly.

Ciao,
Tobias
Comment 2 Mathias 2010-10-22 13:36:49 UTC 
Hi,
I am sorry, but Nepomuk IS running (and doesnt give me that many configuration options). So it must be something els. Two possible reasons:

akonadictl status:
Akonadi Control: running
Akonadi Server: running
Akonadi Server Search Support: available (backend: Unknown)

or

can it be because my akonadi resource points to a single vcf-file as addressbook (because I dont want to loose my categories and distribution lists until they get managable in newer versions of kaddressbook) and kaddressbook cannot handle this properly?