Bug 257607 - autocompletion in the new/edit contact group dialog doesn't work.
Summary: autocompletion in the new/edit contact group dialog doesn't work.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-22 15:32 UTC by Ludwig Reiter
Modified: 2017-01-07 21:50 UTC (History)
3 users (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 Ludwig Reiter 2010-11-22 15:32:28 UTC
Version:           unspecified (using Devel) 
OS:                Linux

version: e5.20101112.1197730-kk4 (enterprise5)

Try to create a new contact group. Not possible to autocomplete a contact from the Kolab resource.

Reproducible: Always

Steps to Reproduce:
1. Create three test contacts in the Kolab resource.
2. Start to create a new contact group.
3. Try to add one of the test contacts from the resource.

Actual Results:  
No autocompletion appears.

Expected Results:  
Autocompletion of existing contacts (and contacts from a LDAP server) should work.
Comment 1 kerub 2011-07-09 07:05:24 UTC
The same is true for:
Version: 2.1.1
OS: Linux

and with a vCard directory resource

Also the autocompletion does then not work for kmail2
Comment 2 Anders Lund 2012-02-01 21:29:07 UTC
I have no LDAP or kolab addressbooks, but I do not understand why they should behave different from other resources in this regard. Autocompletion works fine here (KDe 4.8)
Comment 3 Denis Kurz 2016-09-24 20:53:07 UTC
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.
Comment 4 Denis Kurz 2017-01-07 21:50:25 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.