Summary: | KMail becomes unable to fetch e-mail after trying to view a specific folder | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Arvid <behold> |
Component: | message list | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | major | ||
Priority: | NOR | ||
Version: | 4.14.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Arvid
2015-02-28 15:54:07 UTC
Update: After experimenting some more I found that the issue occurs when I synchronize the folder in general, not only when I actually select it. I was able to work around the issue by changing the folder properties to never sync, and I was thus able to at least read the messages already listed in the folder. I then did a Google search for the gmail address that was printed by Akonadi (the actual address differs slightly from what I wrote above), and found a reference to a specific e-mail to a mailing list I subscribe to. I looked up the message in question in KMail and found that I for some reason had two copies of the same message. I tried simply removing both entries, and after doing so I can now synchronize the folder properly. I am leaving this issue unresolved, however, as I still consider it a bug that KMail stops functioning like this simply because something went wrong with a single e-mail message. It is also likely that another user in the situation would not have been able to resolve this on their own. I have no idea how I could have resolved this issue had I not been lucky enough to find the address outputted by Akonadi on Google. This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input. |