Anyone using Akonadi (Kmail, Kontact) on Debian 13? 👀
ProcessControl: Application "/usr/bin/akonadi_maildispatcher_agent" stopped unexpectedly ( "Process crashed" )
rocessControl: Application "/usr/bin/akonadi_sendlater_agent" stopped unexpectedly ( "Process crashed"
Application '/usr/bin/akonadi_imap_resource' crashed too often. Giving up!
A decade and a half after the first release, #Akonadi remains unusable.
Got pissed off by KMail today, because it stopped sending mails - they just sit there in an outgoing queue and the only way to send them is to restart everything of Akonadi (I already hate Akonadi and I want it to burn to the ground, but this...).
So, starting to evaluate meli to replace all that crap. It's kinda rough, but it works.
Not sure that I'm ready to go mutt/neomutt right away, but we shall see.
If you are using #archlinux, think twice before updgrading (mariadb). Upgrading to v. 12.1.2 will break #akonadi, and thereby #kmail, #kontact, #korganizer etc.
The cause of this is not kmail or akonadi but mariadb. If you experience this, you can downgrade mariadb packages using pacman -U and point it to packages in /var/cache/pacman/pkg/ - the packages mariadb, mariadb-libs and mariadb-clients must be downgraded, adding them on one line is best.
UPDATE I have NOT got this working safely yet.
If you were hit
* close any kdepim app - kmail, kontact, korganizer, kaddressbook, merkuro or other
* stop akonadi - $ akonadictl stop
* remove ALL akonadi related dat from ~/.local and ~/.config. ALL.
* I removed all config, state and app data for kdepim apps as well, before kmail would start cleanly
Repeat until kdepim apps starts cleanly
@rainer Also... wenn man nicht zu exotisches Gebimsel drauftütert, funktioniert so'n Rolling Release wie #OpenSUSE 's #Tumbleweed inzwischen wunderbar. Ich nutze es wohl seit dessen Anbeginn - zuerst war's wirklich manchmal frickelig. Aber inzwischen hab ich gar kein Theater mehr. Im Gegenteil. Und selbst mein "gekauftes" #VuesScanPro läuft mit meinen schon immer bockigen Scannertreibern (Epson) super und ohne jeden Ärger.
Allein, #Kmail bzw. #Akonadi war mitunter etwas "schwierig". Da bockte Kmail nach nem Update schonmal. Allerdings, wenn nicht am Tag drauf, dann am übernächsten war das entsprechende Update da und alles wieder gut - ohne eigenes Nachschrauben.
Mittlerweile empfehle ich es meinen Freunden oder helfe bei der ersten Installation. Danach macht es auch den "Neulingen" gleich spaß. Bis jetzt, jedenfalls. :smile:
@Pabarino wrote about the progress on making the migration service of Merkuro more efficient and not running contently in the background when not using it:
Camp KDE 2010 - Stephen Kelly - Akonadi Models and Proxies: Tips, Tricks, and Hacks
Camp KDE 2010 - Adenilson Cavalcanti - KDE-PIM Google Sync
@cmccullough @markpitblado Aaaah... You've reminded me of those days. I've used Elm, Pine, Alpine and Mutt, but at some point I started using KMail.
Which was fine until quite recently, when its backend, akonadi started to act up, leading to me having to rebuild my setup three times now, from scratch.
And I need to zoom through hundreds of mails a day, so maybe... I'll try aerc, too!
Today's adventures with #Akonadi:
- doesn't wait for network to be up and kwallet to be opened to say “can't download element without network connection” with broken UTF characters,
- throws an error notification thar disappears from the notification centre,
- a moment later says that the PIM module is “not ready for work”, with a start button that does nothing,
- `akonadictl status`: sever stopped,
- `akonadictl start`: server already running,
- `akonadictl fsck`: server not running, no fsck
@Pabarino has published a blog post about his GSoC progress on removing the heavy QtWidgets dependency from Akonadi's background processes. Check it out!
@thelinuxexperiment
I loved KDE until it used plasma ....
But now i have so many problems with it ....
Espacially with #akonadi ... It destroyed to much while using kontact ... ;(
@daveburb with an exception of a few years (~09-12 on Thunderbird) I've been using KMail since its inception exclusively, since none of the alternatives could come close to it.
Sure, I had some fights with its underlying #Akonadi, but what KMail offers in functionality, customizability integration and ergonomics easily made up for it.
#kde #kmail #akonadi
Finally got Kmail working (:
When you add an account you get an initial popup (on first install), so you can hook your account into Kmail. But if you fuck that up somehow (me) and don't check the "can edit, delete and send messages" box, then you just can't do shit. Tried almost everything (including nuking the app and the hook) but it still kept that faulty hook.
How'd I get it working then?
Just delete everything under LibKGAPI inside KdeWallet. Took a day to figure out :P
okay, 5 minutes later, I find out that KOrganizer and Merkuro Calendar both depend on #Akonadi, so I'm going to start by trying the Thunderbird calendar instead. :P
@ts-new Mittlerweile löppt #Akonadi tatsächlich relativ "sturzfrei". Meine Güte, damals... eine Terminanfrage kam als abgelehnt zurück, beim Verschieben aus Kmail raus *Klatsch-Batsch* alles mehr oder weniger unreparierbar zerschreddert. Mailkonto hinzufügen, Fehler im Passwort oder so... Dialog geht dreifach erneut auf und Zack... siehe oben.
Heiße Zeiten damals, hat sich aber wirklich gemausert. Anfangs war es zwar, gerade mit Blick auf #KMail, manchmal ein wahres Drama, aber ich hatte mir damals sogut wie möglich gemerkt, wann welche Probleme aufgetreten waren. Dabei geblieben war/bin ich bis heute.
Denn, den Komfort, den ich (trotz der früheren Probleme) mit Komponenten wie #KAddressbook, #KOrganizer und all den anderen Komponenten genieße, möchte ich nicht mehr missen.
Und mit etwas Glück... ist "Drama, Baby, ja nun einigermaßen gegessen. :smile: