[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

https://bugs.kde.org/show_bug.cgi?id=358364 Denis Kurz changed: What|Removed |Added Status|NEEDSINFO |RESOLVED

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

https://bugs.kde.org/show_bug.cgi?id=358364 Denis Kurz changed: What|Removed |Added Resolution|--- |WAITINGFORINFO

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #2 from Jan Hudec --- Created attachment 96785 --> https://bugs.kde.org/attachment.cgi?id=96785=edit Valgrind memcheck trace I killed kontact after it started (successfully under valgrind). When I then started it, it crashed

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

https://bugs.kde.org/show_bug.cgi?id=358364 Jan Hudec changed: What|Removed |Added Component|general |mail -- You are receiving this mail

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #1 from Jan Hudec --- I am now certain it started after trying to answer email, because when I started it under valgrind it filtered the invalid write and two composers opened. I am attaching the valgrind memcheck output.

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #3 from Jan Hudec --- Created attachment 96786 --> https://bugs.kde.org/attachment.cgi?id=96786=edit One more valgrind trace When I started it next time, one more message editor came up. However the number of invalid writes

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #4 from Jan Hudec --- I closed the message editors when running under valgrind. Since then, kontact starts up correctly again. This workaround isn't for mere mortals, but presumably there might be some way to remove the draft