Bug 265764 - migrators run on every Kontact run when switching to summary view
Summary: migrators run on every Kontact run when switching to summary view
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 4.4
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-08 06:30 UTC by Will Stephenson
Modified: 2017-01-07 21:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Will Stephenson 2011-02-08 06:30:15 UTC 
Version:           4.4.10 (using KDE 4.6.0) 
OS:                Linux

The migrator dialogs (kaddressbookmigrator and kresmigrator) appear during every Kontact run when switching to the summary plugin.  Only the default resources exist, and these appear to have been successfully migrated>

kaddressbookmigratorrc:
[Startup]
EnableAutostart=false

kres-migratorrc:
[Bridged]
calendarResources=
contactResources=

[Resource KOuuSP2xOy]
MigrationState=Complete
ResourceIdentifier=akonadi_ical_resource_1

[Resource XDmifpG4Hv]
MigrationState=Complete
ResourceIdentifier=akonadi_birthdays_resource_0

[Resource s277xKHQJY]
MigrationState=Complete
ResourceIdentifier=akonadi_vcard_resource_1


Reproducible: Always
Comment 1 Will Stephenson 2011-02-08 12:36:54 UTC 
By disabling summaries methodically, I see that both the todo and events plugins cause both migrators to run.
Comment 2 Christophe Marin 2011-02-08 12:48:55 UTC 
*** Bug 263293 has been marked as a duplicate of this bug. ***
Comment 3 Denis Kurz 2016-09-24 20:32: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 21:38:20 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.