Version: unspecified (using KDE 4.7.1) OS: Linux Migration in Kmail2 failed After update from KDE 4.6.5 to 4.7.1. Reproducible: Didn't try Actual Results: When Kmail2 started first time after update there was error message about failed migration and that need to run "kmail-migrator --interactive" manually. But when running "kmail-migrator --interactive" I got error message: Migration of kmailrc has already run, not running it again I restored backup of ~/.kde and figured out that if run "kmail-migrator --interactive" before first start Kmail2 then migration will be successful. But if Kmail2 started first then migration will be failed. Expected Results: Migration should work when starting Kmail2.
Before update to KDE 4.7.1 I have Kmail 1.13.7 installed with KDE 4.6.5. Looks like the same problem also in KDE 4.7.2.
Ok and what is the error ???? it's failed ok but why it failed ?
Created attachment 64384 [details] Kresource Migration Tool When KDE 4.7.1 started firest time after update opened window "Kresource Migration Tool" with message that Migration of 'resource' succeeded.
Created attachment 64385 [details] KMail Migration When I started Kmail "Kmail Migration" opened and I pressed "Migrate Now"
Created attachment 64386 [details] Migration Failed Then appeared this window with error message: Migration to Kmail 2 failed. In case you want to try again , run 'kmail-migrator --interactive' manually. But when I tried this command there was message: Migration of kmailrc has already run, not running it again And I can reproduce this every time when using saved .kde dir.
it doesn't give me info about failed :)
(In reply to comment #6) > it doesn't give me info about failed :) If you tell me what additional information needed and how can I get it then I can provide it here.
So when I running kmail from command line I got this: $ kmail QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kmail-migrator(28579) main: Migration of kmailrc has already run, not running it again kmail2(28576): Akonadi migration failed! kmail2(28576): command was: ("/usr/bin/kmail-migrator", "--interactive-on-change") kmail2(28576): exit code: 4 kmail2(28576): stdout: "" kmail2(28576): stderr: ""
KMail write Version=1 to kmail-migratorrc before start kmail-migrator
(In reply to comment #9) > KMail write Version=1 to kmail-migratorrc before start kmail-migrator And then kmail-migrator fails because of this commit https://projects.kde.org/projects/kde/kdepim-runtime/repository/revisions/db0c79245cec967f5af1c94f62ae377dd0eb81a4
Good catch. So I take it that KMail is broken and needs to be fixed (by removing 1 line?), right?
Created attachment 64509 [details] kdepim-4.7.2-alt-migration.patch fixes the problem
No it's not good this patch. You don't want to migrate => you wrote it. With your patch you can't say no. So it(s not good.
Created attachment 64515 [details] kdepim-4.7.2-alt-migration.patch '("Enabled", false)' may be changed to '("Version", targetVersion)' in first hunk
> '("Enabled", false)' may be changed to '("Version", targetVersion)' in first > hunk Yes, I think you should change that. When/if there will be another migration of this kind needed, the user might want THAT migration to happen.
Created attachment 64523 [details] kdepim-4.7.2-kmail-migration.patch This version of the patch disables only this migration permanently and not future ones (with new target versions.) That said, I'm not convinced that that hunk is correct in the first place. Does a user really expect a "no" to be permanent? I'd expect it to be a "Not now", not a "Never".
(That said, getting prompted again and again with no way to opt out would also be an annoyance, so I guess distros looking for a quick fix should use my patch from comment #16.) By the way, the commit which caused this regression is this commit by David Faure: https://projects.kde.org/projects/kde/kdepim-runtime/repository/revisions/60f8c01542f86bd04cafd68b91c2f609d73d4aa2 which added the check preventing running the migration manually when it was already run.
I tested patch from comment #16. Migration works as expected.
Clearly I have the same bug... but currently I have lost all my mail, and every time I try to start kmail I get the error-message that "Failed to fetch the resource collection"
(In reply to comment #19) > Clearly I have the same bug... but currently I have lost all my mail, and every > time I try to start kmail I get the error-message that "Failed to fetch the > resource collection" Maybe this information can be useful for you https://wiki.kubuntu.org/OneiricOcelot/Final/Kubuntu/Kmail2
Partially helpful, thank you... now I no longer have the "Failed to fetch resource collection" but 1) a collection of error messages during the interactive migration "KMail folders: unusable configuration". 2) a migration request when i start kmail 3) no mails in the correctly transfered directory/folder structure On Mon, Oct 24, 2011 at 5:44 PM, nucleo <nucleo@fedoraproject.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=283563 > > > > > > --- Comment #20 from nucleo <nucleo fedoraproject org> 2011-10-24 15:44:23 > --- > (In reply to comment #19) > > Clearly I have the same bug... but currently I have lost all my mail, and > every > > time I try to start kmail I get the error-message that "Failed to fetch > the > > resource collection" > > Maybe this information can be useful for you > https://wiki.kubuntu.org/OneiricOcelot/Final/Kubuntu/Kmail2 > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. >
Appears not to be fixed in KDE 4.8, at least according to the latest update on the Kubuntu LaunchPad bug entry for this problem: https://bugs.launchpad.net/bugs/857828 # Just incredible that is isn't fixed with a new LTS release. # # My company just decided to stop using KDE due to bosses finding it # unacceptable that people loses emails and configurations due to just # a update. Back to windows.
Git commit 15bd943e1add04435e03f6cdf31b37dd976eb8d1 by Martin Koller. Committed on 01/08/2012 at 19:19. Pushed by mkoller into branch 'KDE/4.9'. Fix for: kmail does never start migration see also https://git.reviewboard.kde.org/r/105788/ FIXED-IN: 4.9.1 M +4 -4 kmail/kmkernel.cpp http://commits.kde.org/kdepim/15bd943e1add04435e03f6cdf31b37dd976eb8d1
Git commit 12f1cfa98eb7c8a0d942bcc09c54ce4289ac95fd by Martin Koller. Committed on 01/08/2012 at 19:19. Pushed by mkoller into branch 'master'. Fix for: kmail does never start migration see also https://git.reviewboard.kde.org/r/105788/ FIXED-IN: 4.9.1 M +4 -4 kmail/kmkernel.cpp http://commits.kde.org/kdepim/12f1cfa98eb7c8a0d942bcc09c54ce4289ac95fd