https://bugs.kde.org/show_bug.cgi?id=374734
--- Comment #36 from Olivier BELLEUX <o.g.m.bell...@gmail.com> --- I confirm that the update does not completely solve the bugs. I received two mail (html newsletters) that were filtered to the right folder but then read them caused a crash; Unable to delete them from kmail; I had to do it by hand since my maildir (my accounts are all in pop3: safer) then: Akonadi fsck Akonadi vacuum Akonadi restart Kontact Tired of this akonadi. Akonadi is an interface between the client and the server ... but when akonadi bugs it becomes a wall between the applications of the kontact suite and servers ... The idea was good but the implementation is far from conclusive: perhaps it is time to replace the too complex and fragile akonadi with a simpler solution such as a module kcm to centralize the management of accounts (kde -pim and telepathy) and stored these configurations in such a way that all software can access these resources directly. In addition kpart k-d-bus technologies would allow a client to access resources through another client. Of course this implies more code and work for each client but in the end it would probably be more KISS and therefore more robust. This does not prevent the use of databases to optimize clients, but several sqlite db may be more robust than a very large mysql db, may not ? Sorry for my comment a bit long but these multiple and recurring Akonadi dysfunction starts to disgust me from Kontact which is the killer apps for which I chose kde instead of gnome 7 years ago. If the situation does not evolve in the right direction then I should resolve to leave kde for gnome: it will be painful to me but if the stubbornness of the kde-pim team to keep alive akonadi persists then it will be bye bye. .. -- You are receiving this mail because: You are watching all bug changes.
