What | Removed | Added |
---|---|---|
Priority | P2 - High | P5 - None |
CC | wbauer@tmo.at | |
See Also | https://bugs.kde.org/show_bug.cgi?id=361157 |
(In reply to Sebastian Kuhne from comment #1) > I am increasing the priority to P2 because I think this is an important bug > which should be fixed soon. You are not supposed to do that, unless you want to handle this bug yourself. This field is for the developers/maintainers to prioritize the bugs the work on. > I am happy to support with log files, etc but the Akonadi structure is quite > complex and I do not know at the moment which information are helpful and > required to help solving this issue. Exactly. And that's why you should better report this to the Akonadi/KDEPIM developers, not us (we basically just package what they release). Regarding the reported problem, I don't see that here and cannot reproduce it either. I am aware of a bug report (https://bugs.kde.org/show_bug.cgi?id=361157) and a long forum thread about similar problems: https://forums.opensuse.org/showthread.php/516850-After-Updating-KDE-FW-to-5-20-and-Plasma-to-5-6-(with-Qt-to-5-6-as-well)-Akonadi-quot-doesn-t-work-quot So far, the most plausible reason (IMHO at least) is some random memory corruption that even seems to be specific to certain CPU models (so it's probably not even a bug in KDEPIM or akonadi, but rather on a lower level). For what it's worth, KDEPIM 16.08.0 has already been submitted to Factory and accepted yesterday, should be in the repos in the next few days. Maybe it improves things.