Bug 339949 - Kontact crashes consistently with one particular mail
Summary: Kontact crashes consistently with one particular mail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-14 07:47 UTC by Sudhir Khanger
Modified: 2018-02-01 09:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash report (12.59 KB, text/plain)
2014-10-14 07:48 UTC, Sudhir Khanger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sudhir Khanger 2014-10-14 07:47:54 UTC
I receive blog posts as email from a program known as rss2email. Kontact has been crashing consistently with one of these particular mail/blog post. 

Reproducible: Sometimes

Steps to Reproduce:
1. Click on this particular email
2.
3.

Actual Results:  
Kontact crashes

Expected Results:  
Kontact shouldn't crash

I am using Kontact 4.14.1 on Plasma 5.0.2 and frameworks 5.2. I wonder if this crash is because of gif in the blog post. http://zaufi.github.io/programming/2014/10/14/kate-cpp-helper-release-1.0.4/
Comment 1 Sudhir Khanger 2014-10-14 07:48:37 UTC
Created attachment 89124 [details]
crash report
Comment 2 Denis Kurz 2017-06-23 19:36:14 UTC
This bug has never been confirmed for a Kontact 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-02-01 09:53:55 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 much more recent), please open a new one unless it already exists. Thank you for all your input.