Bug 226387 - Addressbook (Contacts resource) is shown twice
Summary: Addressbook (Contacts resource) is shown twice
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-11 21:15 UTC by Christoph Lange
Modified: 2017-01-07 22:45 UTC (History)
2 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 Christoph Lange 2010-02-11 21:15:15 UTC
Version:           4.4 (using 4.4.00 (KDE 4.4.0), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.31-thinkpad

I have one addressbook (“contacts”) resource.  It comes from the pre-Akonadi times and therefore is a file.  It's fine if it remains a file, because I would like to sync it with other computers.

In the system settings, this resource is named "Default Addressbook", it is set as standard “contacts” resource, and it maps to the vCard file ~/.kde4/share/apps/kabc/std.vcf.  The latter file is BTW a symlink, as I need that for my syncing setup, which goes via a Subversion repository.

In the left column of the KAddressBook main view, I see two address books: “Default Addressbook” and “std.vcf”, even though both are the same.
Comment 1 Tobias Koenig 2010-02-11 21:48:26 UTC
The second address book has been added by the migrator,
it is safe to simply remove the std.vcf resource
Comment 2 Thomas McGuire 2010-02-12 14:08:09 UTC
Not invalid, but a migration bug.
Comment 3 Denis Kurz 2016-09-24 20:43:05 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:45:01 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.