Summary: | Mail Dispatcher Agent went offline for unknown reason | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Alexander van Loon <a.vanloon> |
Component: | Mail Dispatcher Agent | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | Mathias.Homann, peter, piedro.kulman, remur, tiposchi, vkrause |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alexander van Loon
2011-12-09 22:18:04 UTC
I'm having the same issues in KDE 4.9.4 here. After a few hours of working with my computer the mail dispatcher simply stops working and needs to be restarted. I have a similar problem with KDE 4.10.4 - the mail dispatcher agent is shown allright and online in the Akonadi console but it doesn't work. I have to manually restart the agent (i do that in akonadi console "restart agent") and it works again ... IMHO this is again a seríous problem - mail that has been sent stuck in the outbox is a real show stopper ... p. Plz, can someone confirm this? I run KDE on Arch, it's version 4.10.5. This bug is not random: Anytime I leave my box running for more than a day (this is an estimate) the akonadi agent has to be restarted. And, by the way, this is true for: - mail dipatcher agent - mail filter agent (filtering always stops at a certain runtime) - local notes (for kjots: it stops showing the notes altogether and has to be restarted to work again) - ... there may be more but these are the agents I use mostly use Years ago I had a similar problem. That had to do with the missing entry "wait_timeout=31536000" in the mysql.conf. But now I checked in the folder "~/.local/share/akonadi" - the file "mysql.conf is present and has the above entry. thx for reading, piedro I am having the same problem now. Actually, maybe it's different since my one refuses to go online. This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |