Incidentally, is there a resistance movement to get Akonadi out of KDE that
I could join and/or finance? The Internet seems pretty unified that the Akonadi experiment has been a catastrophic failure and has left Linux
source without a proper PIM suite since 2008.
Jokes aside, did you roll back PostgreSQL to 13 and purge all Akonadi-related packages, then reinstall them? This worked for me (the purging and reinstalling part) the first time it broke down.
I made the grave mistake of upgrading from PostgreSQL 13 to 14 and assuming that Akonadi would upgrade, too. This, of course, broke Kontact and all of its sub-programs, so I deleted everything I could find in ~/.local/share/akonadi* , ~/.config/akonadi* , ~/.cache/akonadi* and a few kmail2 files that looked safe to delete.
1) Akonadi keeps downloading from my IMAP account at top speed (thereby hogging all the available bandwidth on my network) and never seems to
finish.
2) Akonadi no longer recognises my Maildir as a KMail Mail Folder
and refuses to sync the subfolders. However, I can load my Maildir as a simple Maildir folder.
3) Akonadi no longer loads contacts from any of my
vCard dirs
By the way, ~/.config/akonadi* are configuration files! So you hopefully have backup those, as I expect two of your problems would been fixed, if you recover those files.
1) Akonadi keeps downloading from my IMAP account at top speed (therebySure it needs to download every mail again from your IMAP account.
hogging all the available bandwidth on my network) and never seems to
finish.
2) Akonadi no longer recognises my Maildir as a KMail Mail FolderThe default settings have changed in between several KDEPIM versions, this is what is stored in .config/akonadi/ files. Recover those files from backups, than these two resources are availalabe again, after you restarted Akonadi.
and refuses to sync the subfolders. However, I can load my Maildir as a
simple Maildir folder.
3) Akonadi no longer loads contacts from any of my
vCard dirs
By the way, ~/.config/akonadi* are configuration files! So you hopefully have backup those, as I expect two of your problems would been fixed, if you recover those files.
Not a problem. I made sure I read the files and wrote down any important information before deleting them. I should be able to rebuild these because Akonadi doesn't touch the underlying data (right? RIGHT?!). It's sometimes just easier to start fresh, which is what I want to do, anyhow.
1) Akonadi keeps downloading from my IMAP account at top speed (thereby
hogging all the available bandwidth on my network) and never seems to
finish.
Sure it needs to download every mail again from your IMAP account.
The trouble, though, is that it _has_ finished downloading every message,
and it continues to download. Perhaps there's a server side error, perhaps there's a KMail error. I just don't know how to navigate the Akonadi
console to find what's causing the traffic jam.
2) Akonadi no longer recognises my Maildir as a KMail Mail Folder
and refuses to sync the subfolders. However, I can load my Maildir as a
simple Maildir folder.
3) Akonadi no longer loads contacts from any of my
vCard dirs
The default settings have changed in between several KDEPIM versions, this is what is stored in .config/akonadi/ files. Recover those files from backups, than these two resources are availalabe again, after you
restarted Akonadi.
I could have followed this advice yesterday before, in an unrelated
incident, I accidentally destroyed my most recent backups by resizing partitions (hint: moving btrfs partitions is not a failsafe operation!) :-P
I don't mind rebuilding the databases. If I can figure out what the
maildir and vCard directory plugins are choking on, I might be able to fix the offending files by hand and/or file an intelligent bug report. But, again, I don't know which logs to review.
run Akonadi with logging enabled:
QT_LOGGING_RULES="*=true;qt.*=false" akonadictl restart
or even log the complete IMAP traffic:
export KIMAP_LOGFILE=/tmp/imap.log
QT_LOGGING_RULES="*=true;qt.*=false" akonadictl restart
see also > https://techbase.kde.org/KDE_PIM/Akonadi/Debug_IMAP
I managed to work around this problem by right-clicking the offending IMAP account, clicking Folder Properties -> Retrieval Options and selecting "Retrieve message bodies on demand". I think what happened is that the server timed out and instead of1) Akonadi keeps downloading from my IMAP account at top speed (thereby >> >> hogging all the available bandwidth on my network) and never seems to
finish.
Sure it needs to download every mail again from your IMAP account.
The trouble, though, is that it _has_ finished downloading every message,
and it continues to download. Perhaps there's a server side error, perhaps >> there's a KMail error. I just don't know how to navigate the Akonadi
console to find what's causing the traffic jam.
see also https://techbase.kde.org/KDE_PIM/Akonadi/Debug_IMAPThis automagically updated in the latest testing dist-upgrade, so I think there was a regression or library conflict that eventually resolved. This works now.
2) Akonadi no longer recognises my Maildir as a KMail Mail Folder
and refuses to sync the subfolders. However, I can load my Maildir as a >> >> simple Maildir folder.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 88:33:40 |
Calls: | 6,658 |
Files: | 12,203 |
Messages: | 5,333,956 |