Every-time I click on New Message, Kontact closes. However, the system doesn't seem to recognise it as a crash. To send a new message, I have to reply to an old message and change all the fields. My system is Kubuntu 16.04 (Xenial) running Kontact 5.0.2 (I cant find this version in the Scroll box above). Please advice how to get a proper bug report. Reproducible: Always Steps to Reproduce: 1. Open Kontact 2. Click on the "New Message" button Actual Results: Kontact terminates Expected Results: Display a window were I can write a new email message
I just run kontact from the terminal and managed to get this before it crashed log_templateparser: AKONADI PORT: verify Akonadi::Item() here virtual QString TemplateParser::TemplateParser::findTemplate() log_templateparser: AKONADI PORT: verify Akonadi::Item() here virtual QString TemplateParser::TemplateParser::findTemplate() log_templateparser: Identity found: 199918551 log_messageviewer: Node UNprocessed: 0x3355ae0 log_messageviewer: BodyPartFormatterFactory: found 4 plugins. log_messageviewer: BodyPartFormatterFactory: instantiating new Subtype Registry for " text " log_messageviewer: SET NODE: 0x3355ae0 true log_messageviewer: Node processed: "" "Content-Type: text/plain; charset="utf-8"" log_templateparser: Command: REM= log_templateparser: Command: - log_templateparser: Command: BLANK log_templateparser: No appropriate charset found. log_messagecomposer: initalising autosave Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. HSpellDict::HSpellDict: Init failed "contactsCompletionSession" connectToServer "/tmp/akonadi-<myusername>.bqg6UD/akonadiserver.socket" Pass a valid window to KWallet::Wallet::openWallet(). log_kmail: log_kmail: "<my email address>" *** KMail got signal 11 (Exiting) Segmentation fault (core dumped)
Probably duplicate of https://bugs.kde.org/show_bug.cgi?id=355093
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based 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 opportunity 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 much more recent), please open a new one unless it already exists. Thank you for all your input.