Bug 312150 - kmail autocompletion doesn't find all addressbook entries - namely not the ones containing the address of a web page
Summary: kmail autocompletion doesn't find all addressbook entries - namely not the on...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdepim
Classification: Applications
Component: libkdepim (show other bugs)
Version: GIT (master)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on: 259949
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-24 08:06 UTC by Knut Hildebrandt
Modified: 2013-04-08 16:13 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Hildebrandt 2012-12-24 08:06:21 UTC
Since a few releases kmail autocompletion, even though it sometimes behaves strangly, seems to work for me. But recently I noticed that some addresses are never found. A little research into the matter revealed, that all of these contacts had one thing in commen. All of them contained the address of a web page. Once I deleted this address, kmail could find the mail addresses contained in these contact informations. It even continued doing so, when I added the address of the web page again.

Also could confirm this behaviour after creating new contacts.
 

Reproducible: Always

Steps to Reproduce:
1. create new contact
2. add mail address
3. add web page
4. try autocompletion in kmail (doesn't work)
5. delete web page
6. try autocompletion in kmail (it works)
7. add web address again
8. try autocompletion in kmail (it still works)
Actual Results:  
Eventually I got kmail autocompletion working. 

Expected Results:  
Autocompletion should always work for all contacts regardless if they contain the address of a web
page or not and without using funny workarounds.
Comment 1 Christian Mollekopf 2013-01-31 12:24:46 UTC
According to https://bugs.kde.org/show_bug.cgi?id=259949#c285 contacts with a website are indexed as rdfs:Resource instead of nco:PersonContact
Comment 2 m.wege 2013-01-31 13:09:47 UTC
I can confirm this problem.
Comment 3 Christian Mollekopf 2013-02-19 10:10:04 UTC
I can't reproduce this problem with 4.10.
Comment 4 Knut Hildebrandt 2013-03-20 01:47:32 UTC
Seems to work for me as well since recent update to 4.10.1.
Comment 5 Knut Hildebrandt 2013-03-20 01:49:40 UTC
Seems to work without problems since recent update to 4.10.1.
Comment 6 Knut Hildebrandt 2013-03-20 01:51:09 UTC
(In reply to comment #1)
> According to https://bugs.kde.org/show_bug.cgi?id=259949#c285 contacts with
> a website are indexed as rdfs:Resource instead of nco:PersonContact

Seems to work without problems since recent update to 4.10.1.
Comment 7 Knut Hildebrandt 2013-03-20 10:17:32 UTC
(In reply to comment #3)
> I can't reproduce this problem with 4.10.

Since the update to 4.10.1 the problem seems to be gone.