Akonadi is getting confused?
Page 1 of 1 (6 posts)
Tags:
None
KDE Developer 
|
I use KMail2 as my email client all the time. Abiut once a month I comb through my "inbox" file to move some messages to trash, and others to the appropriate archival folder. I have ~35,000 emails saved in the whole directory tree. Oh -- I'm running Gentoo Linux, KMail 5.16.3 (20.12.3), KDE Frameworks 5.80.0, Qt 5.15.2, and KDE Plasma 5.20.5.
I think this may be a bug related to the 20.12.3 packages. I compiled / installed those on April 6. There were a lot of them. Both Akonadi and KMail2 were rebuilt that day. This is the first time I have cleaned up my inbox since the new version went in almost a month ago. I'll file this as a bug if I can't learn much in the forum -- just thought that since this is easier, I'd try here first. Plus Ben Cooksley tells me that if I create enough posts in this forum, I'll be allowed to create a signature on my profile page.  Anyway, everything was going fine until I tried to move a certain message to trash. I saw a brief warning message "Moving to trash failed". After that, three messages became inaccessible. When I try to open these messages, I get a different error message:
The other two affected messages show the same error, with a different Akonadi ID / item code, and a different file name. I can locate the files the messages are talking about, in .local/share/local-mail/inbox/cur, and all three messages are there. And they correspond with the inoperative entries in KMail's message list. So whatever is causing the hangup must be part of Akonadi's behind-the-curtain voodoo. As luck would have it, I had stopped the Akonadi serrver and restarted it in a terminal window when this problem arose. I had a similar problem earlier today, so I had rebooted my system and was being a bit careful while trying (again) to clean up the inbox. Here's some terminal output that appears to be relevant.
Any suggestions will be received with gratitude. Thanks! -- David Bryant Canyon Lake, Texas https://davidcbryant.net |
Registered Member
|
I am not able to help much in detail but I recently stumbled upon a post mentioning something similar.
It seems there is a history of data loss with Akonadi and possibly Bug #360834 is the one related to your issues. You could try to run akonadictl fsck to obtain further debug info. |
|
KDE Developer
|
Thank you for the suggestion. I had already done that. And I filed bug reports with Gentoo, and at KDE's bugzilla page. I've been using KMail since 2003, so I'm pretty familiar with all the belly-aching about Akonadi. This isn't even the worst trouble it has ever caused me. But it's close. Here's some terminal output.
That was yesterday. I noticed that the "dirty items" were the messages that I couldn't display. I closed KMail, copied my messages to a backup location, then cleared most of my messages out of the "live" KMail directory structure (~.local/share/local-mail on my Gentoo system). Luckily for me, only a few of the "dirty" items were in KMail's "native" folders (inbox, outbox, sent-mail, trash, drafts, & templates). It's easy to deal with the messages in "custom" folders -- you can just use Dolphin with "cut" and "paste" on entire folders. With the "native" folders you have to cut and paste individual files. Anyway, after I had cleared the "dirty" messages from KMail's directories, I started KMail, forcing Akonadi to erase most of the internal pointers to its relational database structure. I closed KMail and stopped Akonadi, then moved the messages back into the "live" directory. This time when I restarted KMail all the "dirty" items had been fixed. I had to open my message folders one by one to force Akonadi to rebuild its relational database pointers ... that took quite a while, because I had about 100 folders to process. But today it's all patched up.
-- David Bryant Canyon Lake, Texas |
|
Registered Member
|
I sometimes get ghost emails in kmail - they look like duplicates and cannot be deleted
however I found that I can remove them as follows 1. get the mysql process used by akonadi
2. extract the socket part
3. build a sql statement ❯ cat akonadictl.sql
4. put it all together
HTH |
|
KDE Developer
|
The procedure you described has recently been added to the KMail documentation. It should show up in the 21.08 release of KMail  .https://docs.kde.org/trunk5/en/kmail/km ... error.html |
Registered Member
|
You can do it in akonadiconsole, register "DB Console" as well.
|
Page 1 of 1 (6 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]
