Bug#727800: kmail: KMail goes bonkers following Qt update
So, I've tried again, this time restarting Akonadi when the migration script
said it was done. I tried two variations:
1) akonadictl restart before pressing "ok" on the window showing the kmail
resource migration. Surprisingly, this did not cause KMail to shut down. It
also didn't really work -- I ended up with two "KMail Folders" collections,
repeated "item belongs to two top-level collections" error messages, and other
misbehaviors. The two KMail Folders collections contained, each, all my
folders, but it seemed the folders didn't quite work in any of them; I think
inbox looked like it had the right contents in one, but I couldn't get
contents in any other. Maybe I just didn't wait enough (see below).
2) When the migration script says it's done, press ok, close KMail, and then
restart Akonadi. This worked -- in the sense that I got a single "KMail
Folders" collection with all my folders. However, it postponed the action of
actual migration -- when I tried to access the folders, only then KMail did
the actual loading and syncing or whatever takes so long. Opening a folder
with ~22000 mails took well over 5 minutes, and during these minutes, no other
mail could be retrieved (even from the inbox which had already been synced
before).
Still, no filters were migrated. None whatsoever. I have ~30 of them.
I am writing this message from the upgraded user -- as a test to see if the
other bug I'm experiencing (sending requires akonadi restart) is specific to
my "regular" user. I encountered another issue -- although my Identity has
"sign messages automatically" set to False, when I started writing the "sign
message" option was on. Perhaps it was on in the last message I sent before
doing the backup from which this user is restored, I'm not sure. Either way,
it was surprising.
Hope this helps,
Shai.
Reply to: