Bug 348409 - KMail crashes on reply
Summary: KMail crashes on reply
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.14.7
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-29 17:39 UTC by Michael
Modified: 2018-01-31 16:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Mail which leads to reply stuck/crash (181.43 KB, text/plain)
2015-05-29 17:44 UTC, Michael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2015-05-29 17:39:41 UTC
KMail crashed after I pressed the reply button on a certain mail. Well it opened a reply didn't respond and I had to kill it.
One time, it wasn't even possible to restart kmail. The prepared reply templates were already saved in .kde/share/apps/kmail/autosave and deleting them helped to make kmail restart again.

I would like to provide the particular E-Mail, maybe it is a rendering problem (well, just displaying works fine) or conversion problem, when creating the reply-text in the reply-window. But unfortunately it is not possible to upload a file here.

I hope this is just a simple bug in kmail and not again an issue concerning this excruciating akonadi framework.


Reproducible: Always

Steps to Reproduce:
1. Reply to certain mail
2. KMail stucks, kill it
2.5 Delete files in .kde/share/apps/kmail/autosave if you want it working again
3. Reopen Kmail



Unspecific Output from restarting KMail into the stuckness due to malign files in autosave:

mf@koi:~$ QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kmail2(26020): No language dictionaries for the language :  "de" 

kmail2(26020): No language dictionaries for the language :  "de" 

kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-excel.sheet.binary.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-excel.addin.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-powerpoint.slideshow.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-excel.sheet.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-powerpoint.presentation.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-word.template.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-excel.template.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-powerpoint.template.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-word.document.macroEnabled.12" 
kmail2(26020) KMimeTypeRepository::parents: "/usr/share/mime/subclasses"  refers to unknown mimetype  "application/vnd.ms-powerpoint.slide.macroEnabled.12" 
kmail2(26020): No language dictionaries for the language :  "de" 

kmail2(26020): No language dictionaries for the language :  "de"
Comment 1 Michael 2015-05-29 17:44:22 UTC
Created attachment 92909 [details]
Mail which leads to reply stuck/crash
Comment 2 Denis Kurz 2017-06-23 19:55:57 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those 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 oportunity 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 3 Denis Kurz 2018-01-31 16:51:36 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.