http://bugzilla.opensuse.org/show_bug.cgi?id=995911 http://bugzilla.opensuse.org/show_bug.cgi?id=995911#c2 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None CC| |wbauer@tmo.at See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=361157 --- Comment #2 from Wolfgang Bauer --- (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... 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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=995911 http://bugzilla.opensuse.org/show_bug.cgi?id=995911#c4 --- Comment #4 from Sebastian Kuhne --- Wolfgang, many thanks for taking care, and for your hints and comments. I will wait for KDEPIM 16.08.0, and hope that this will probably solve the issue. If not I assume that the other two mentioned bug reports are tracked properly since technically more advanced. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=995911 http://bugzilla.opensuse.org/show_bug.cgi?id=995911#c6 --- Comment #6 from Krasimir Ivanov --- It is nice that kdepim 16.08.0 solved this issue in Tumbleweed for Sebastian. Nice to know it helped him. Unfortunately now I have KMail 5.3.0 and in my Yast I see kdepim 16.08.0-1.1 and same problem still exist here. May be in my case some thing else also need to be changed, but I can not understood what else may be reason for this troubles. Probably I could try a new clean installation of Tumbleweed and will check it after it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=995911 http://bugzilla.opensuse.org/show_bug.cgi?id=995911#c8 --- Comment #8 from Krasimir Ivanov --- Dear Wolfgang, Thank you very much for your reply! I have removed the things you have suggested, then added the repository mentioned in kde.org and after it have updated the Xapian and all akonadi packages. Now finally I can dead my E-mails and work normally with Contact! I am crossing fingers for guys at KDE to fix this nasty issue till the new Tumbleweed update. Thank you very much in helping me. Hopefully it may help to others who will read this information. With best regards, -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=995911 http://bugzilla.opensuse.org/show_bug.cgi?id=995911#c10 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |DUPLICATE --- Comment #10 from Wolfgang Bauer --- As the reported problems have been fixed by installing the older Xapian (and akonadi packages built against it) from the repo Christian Boltz provided, this is actually a duplicate of bug#997246, so marking it as such. FYI, this should finally be fixed in 16.08.2, which is to be released next Thursday. Of course it will take a little bit longer for it to reach Tumbleweed. *** This bug has been marked as a duplicate of bug 997246 *** -- You are receiving this mail because: You are on the CC list for the bug.