Summary: | Akonadi wants to establish IMAP connection although it should not | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Silver Salonen <silver.salonen> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | conrausch, gianted, martin+kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | post mortem crash report |
Description
Silver Salonen
2010-12-12 10:46:07 UTC
Hi, how did you set your accounts to be offline when kmail is off? I can't seem to find this option. I see this behavior too and I agree that it is weird (however completely understandable given the akonadi concept). It's under KMail's Account settings and Retrieval Options: "Switch Offline on KMail Shutdown". this bug was useful for me to find out about this option ("set offline on kmail shutdown". what i find much more annoying about this behaviour is that akonadi is apparently not able to handle connection interruptions, so when i restart kmail it cannot refresh imap folder contents but also does not give any information or error message whatsoever about this, which can lead to the assumption that there is no new mail when really akonadi just can't handle to reconnect... but i guess this would be a different bug report I've found the same behavior also in my Kubuntu 11.10: Application: akonadi_imap_resource (4.7) KDE Platform Version: 4.7.3 (4.7.3) Qt Version: 4.7.4 Operating System: Linux 3.0.0-15-generic i686 Distribution: Ubuntu 11.10 I will attach a crash report. If not OT, I suggest to raise the severity to "crash" (even if I will try with the workaround "set offline on kmail shutdown"). Created attachment 66820 [details]
post mortem crash report
see also inside the attachement for troubleshooting purposes.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 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. |