Summary: | imap_resource crash after manual check | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | jacob.becker |
Component: | IMAP resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | CONFIRMED --- | ||
Severity: | crash | CC: | freekdekruijf, jacob.becker, me |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
jacob.becker
2019-11-30 13:32:51 UTC
I am experiencing same issue in Archlinux since the last major upgrade of KDE Apps: Qt: 5.13.2 KDE Plasma: 5.17.4 Frameworks: 5.64.0 KDE Applications: 19.12.0 In my case I don't need to refresh, it just crashes after some time in a random manner. What seems to fix it (for some time) is doing this: akonadictl fsck akonadictl vacuum akonadictl restart As it was proposed to try here: https://bbs.archlinux.org/viewtopic.php?id=251405 What is strange is that it only affect one of my accounts (it is not Gmail btw). I have contacted my hosting provider to get the details about the IMAP servers they used for my account. This is the info they sent me: # dovecot --version 2.3.7.2 (3c910f64b) # exim --version | head -1 Exim version 4.90 Today I realized that my issue only seems to appear when I leave the computer locked. If I don't lock the computer, Kmail keeps working and there is no crush. If I lock it, after a while imap resource crash and I have to close Kmail, do a akonadictl fsck + vacuum + restart, and then open again Kmail. Maybe some issue with akonadi and lockscreen since last release? Any news about this? This bug report looks like a duplicate of bug 403391 In my case, it got solved with the patch that solved bug 415339 Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! (In reply to Justin Zobel from comment #7) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! This bug looks like bug 425619, which was recently updated with a new backtrace. |