Bug 318028

Summary: autocompletion of mail addresses not working, also groups not working
Product: [Applications] kmail2 Reporter: Orion <orion2000za>
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: major CC: gerdfleischer, gtwilliams, valtermura, woebbeking
Priority: NOR    
Version: 4.10.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 4.10.3
Sentry Crash Report:

Description Orion 2013-04-08 11:55:36 UTC
After upgrade from 4.10.1 autocompletion of mail recepients from addressbook Personal Contacts once again does not work. Only "recent addresses" are suggested.

Also sending to Groups/Distribution lists does not work as they do not get "expanded"

Reproducible: Always

Steps to Reproduce:
1. Compose a new mail
2. in the "To" field start typing
3.
Actual Results:  
only recepients from "recent addresses" gets suggested
If you try using a Group/List it will not be "expanded" and will bounce

Expected Results:  
contacts from Addressbooks should be suggested as in 4.10.1, Groups should be "expanded" on sending

this is once again a regression and I must say it is a "dealbreaker" for me that this comes back once more
Comment 1 Garry Williams 2013-04-08 12:15:50 UTC
I can confirm the bug here:

kdepim-libs-4.10.2-1.fc18.x86_64
Comment 2 Gerd Fleischer 2013-04-08 12:55:12 UTC
Me too with openSUSE Release:410 with 4.10.2
Comment 3 Valter Mura 2013-04-08 18:54:24 UTC
I confirm the bug with KDE 4.10.2:
- recent addresses autocompletion: activated and working
- use of "akonadi_googlecontacts_resource" (setup and correctly working, I mean syncronization)
- in Gmail Contacts I have only two groups: My Contacts & Other Contacts

Note: if I manually select the address (i.e., I click the Select button), and I start writing, the (Gmail) addresses are immediately found)
- nepomuk_feeder: working
- Akonadi: normally working
Comment 4 Orion 2013-04-08 19:20:49 UTC
see 
https://bugs.kde.org/show_bug.cgi?id=259949#c352

a fix has been found and committed to version 4.10.3 so I set this to resolved.

for version 4.10.2 one can use a workaround described in kdeforums here:
http://forum.kde.org/viewtopic.php?f=215&t=110729#p262658