Bug 355093

Summary:	Crash if I click on new mail
Product:	[Applications] kmail2	Reporter:	Ramon <rferremontoya>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	anmeldungen, dwilson, filip.valder, kdenis, klaus.rombach, martin.tlustos, montel, public, saleck, tonymt00, yasinzaehringer+kde
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Console output of crashing KMail after starting KMail2 and composing new email Console output of crashing KMail after starting KMail2 and composing new email log Screenshot Systeminfo gdb backtrace

Description Ramon 2015-11-09 17:17:45 UTC

log_templateparser: AKONADI PORT: Disabled code in   virtual QString TemplateParser::TemplateParser::findTemplate()
log_templateparser: Folder found: Collection ID: 23    remote ID: ".INBOX" 
   name: "INBOX" 
   url:  QUrl( "akonadi:?collection=23" )  
   parent: 15 "imap://rferre@domain.com@imap.domain.com/" 
   resource: "akonadi_imap_resource_0" 
   rights: QFlags(0x1|0x2|0x4|0x8|0x10|0x20) 
   contents mime type: ("message/rfc822", "inode/directory") 
   isVirtual: false 
    CachePolicy:  
   inherit: true 
   interval: 5 
   timeout: 60 
   sync on demand: true 
   local parts: ("ENVELOPE", "HEAD") 
    CollectionStatistics: 
   count: 2191 
   unread count: 0 
   size: 235063934
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: 541682663
log_messageviewer: Node UNprocessed:  0x11467e0
log_messageviewer: SET NODE:  0x11467e0 true
log_messageviewer: Node processed:  "" "Content-Type: text/plain"
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
No language dictionaries for the language: "ca"
"contactsCompletionSession"
connectToServer "/tmp/akonadi-rferre.c2b6Mu/akonadiserver.socket"
No language dictionaries for the language: "ca"
No language dictionaries for the language: "ca"
No language dictionaries for the language: "ca"
No language dictionaries for the language: "ca"
log_kmail: 
log_kmail: "Ramon Ferré"
*** KMail got signal 11 (Exiting)
Violació de segment (bolcat de la imatge del nucli)


Reproducible: Always

Steps to Reproduce:
1. Open Kmail
2. Click on New Mail

Actual Results:  
Closes kmail

Expected Results:  
Write an email

Comment 1 Laurent Montel 2015-11-09 20:14:47 UTC

Backtrace please 
+ kdepim version

Comment 2 Jan 2015-11-11 06:47:20 UTC

KMail Version 5.0.2
KDE Frameworks 5.15.0
Qt 5.4.2

Comment 3 Jan 2015-11-11 18:18:26 UTC

Created attachment 95446 [details]
Console output of crashing KMail after starting KMail2 and composing new email

Comment 4 Jan 2015-11-11 18:33:07 UTC

Created attachment 95447 [details]
Console output of crashing KMail after starting KMail2 and composing new email

Comment 5 Jan 2015-11-12 06:51:28 UTC

After changing "[Spelling]Language=de_DE_frami" into "[Spelling]Language=de_DE" in the .config/kmail2rc file, it seems like I can compose new emails.
As I have change some other things on the system at this time, I'm not really sure if this was causing the crashing of KMail.
Maybe Ramon can confirm this?

Excerpt from Ramon's crash log:
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
HSpellDict::HSpellDict: Init failed
No language dictionaries for the language: "ca"

Excerpt from my first crash log:
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
HSpellDict::HSpellDict: Init failed
No language dictionaries for the language: "de-DE"

I have installed hspell and created symlinks for de-DE and replaced hunspell-de-de-frami packed with hunspell-de-de:
sudo ln -s /usr/share/hunspell/de_DE.dic /usr/share/hunspell/de-DE.dic
sudo ln -s /usr/share/hunspell/de_DE.aff /usr/share/hunspell/de-DE.aff

Comment 6 Klaus 2015-11-29 18:55:19 UTC

Created attachment 95808 [details]
log

Comment 7 Klaus 2015-11-29 19:05:21 UTC

Created attachment 95809 [details]
Screenshot Systeminfo

I must confirm this issue :-( 
Pressing "new mail" crashes kmail.
See also attached log file and screenshot for system informations.

kubuntu was upgraded from 15.04 to 15.10 before. Since that the issue appears. Sometimes it's possible to create a new email.

Remark: There was installed hunspell-de-de all the time.

Comment 8 Gerhard Lehnhoff 2015-12-01 11:29:25 UTC

Same problem (Kubuntu 15.10, Kontact 5.0.2, KMail 5.0.2)

Comment 9 Yasin Zähringer 2015-12-18 11:02:06 UTC

Created attachment 96162 [details]
gdb backtrace

Comment 10 Yasin Zähringer 2015-12-18 11:11:50 UTC

The gdb backtrace indeed shows that the problem is somehow caused by to the spell checker. However, I would like to add that I can reply to emails just fine. And the spell checker is automatically enabled.

Comment 11 Martin Tlustos 2016-01-08 15:47:03 UTC

After you reply to an email, you can then click on "new" without problems (but only in that folder!).

Comment 12 filip.valder 2016-02-29 17:47:07 UTC

I can confirm this annoying bog 

(In reply to Martin Tlustos from comment #11)
> After you reply to an email, you can then click on "new" without problems
> (but only in that folder!).

Comment 13 David 2016-03-21 07:52:03 UTC

Kmail was working for me up until yesterday. I've tried resetting all languages back to American, disabling all autocorrection and spell checkings but starting a New Mail still kills the app completely!

Comment 14 David Brůha 2016-03-29 21:34:57 UTC

Same here - Kubuntu with KMail version 5.0.2, started today

Comment 15 Denis Kurz 2017-06-23 20:53:15 UTC

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.

Comment 16 Denis Kurz 2018-01-31 16:49:54 UTC

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 more recent), please open a new one unless it already exists. Thank you for all your input.