Summary: | Akonadi Agents hang or freeze after more than 24 hour uptime | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | piedro <piedro.kulman> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | kdenis, leggis, piedro.kulman |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
piedro
2013-07-11 08:50:44 UTC
Now I've setup a new installation and this is reproducible. After a long uptime (70 hours this time) the mail dispatcher agent doesn't work. The mail I just sent, stuck in the outbox, akonadi console dooesn't give any reason to believe there is something wrong with the mail dispatcher agent. Clicking on "restart agent" immediately sends out the mail and further mails are also sent without any problems ... plz, which files do I have to edit or delete to get a working akonadi configuration that doesn't stop working after long uptimes. How can I find any protocol on these matters .. Would someone plz confirm or is noone using kmail with long uptimes? I can't believe I am the only one having this problem as I used a fresh install to confirm. thx, piedro Confirm this bug on KDE 4.11.3 It lasts long. I use suspend on laptop all the time. Mail dispatcher agent is seems like online and working, but all sending mails are hangs in local outcoming mail folder. I used to add this folder for favorites to see when I should restart mail dispatcher. Sending mails via kmail take a lot more actions rather via web:( 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. I switched to gnome for productive work, sry, I can not provide anymore specific information on later versions... thx anyway, p. 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. |