Bug 268667 - Diffrent address book lists between KAddress Book and KOrganizer
Summary: Diffrent address book lists between KAddress Book and KOrganizer
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-16 18:09 UTC by Viviana
Modified: 2017-01-07 22:18 UTC (History)
2 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 Viviana 2011-03-16 18:09:52 UTC
Version:           unspecified
OS:                Linux

When I try to add an Attendee from Select Addresse the button appears an old address book not the same that appears when I use the KAddressBook. Theres is a way to synchronize both databases or have an idea the source of the information used by Korganizer.

By the way Im using Kontac 4.4.8, KOrganizer 4.4.8 and KAddressBook 4.4.8 and my OS is Linux 10.04 LTS . Im also using Gnome 2.30.2 not KDE

Reproducible: Always

Steps to Reproduce:
1. Edit or create an event at the calendar of KOrganizer
2. Add Attendees from the Select Addresses butoom


Actual Results:  
The address book list is not the same that appears in the KAddressBook apps

Expected Results:  
Show the same list or let config the source of information.
Comment 1 Anders Lund 2012-02-01 18:11:53 UTC
This appears to be fixed in KDE 4.8 (or earlier), korganizer uses the same dialog as kmail for selecting contacts. Is it Ok to cloce this one?
Comment 2 Denis Kurz 2016-09-24 20:51:58 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 3 Denis Kurz 2017-01-07 22:18:15 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.