Bug 324310 - crash when viewing chinese/gb2312 encoded spam message
Summary: crash when viewing chinese/gb2312 encoded spam message
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-31 08:27 UTC by Henri Valta
Modified: 2013-08-31 09:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
The crash causing mail gzipped (1.48 KB, application/gzip)
2013-08-31 08:28 UTC, Henri Valta 		Details
Partial backtrace (8.30 KB, text/plain)
2013-08-31 08:29 UTC, Henri Valta 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Henri Valta 2013-08-31 08:27:27 UTC 
clicking the message or even hovering mouse over it until the tooltip shows, crashes kmail.

Message in the folder view shows chinese characters in subject and sender. Seems to be gb2312 encoded.

I'll try to attach the message and partial backtrace here. Creating full backtrace seems to take a bit of work on arch... I'll create it if required

Reproducible: Always

Steps to Reproduce:
1. try to view or hover mouse over the message in message list
2.
3.
Actual Results:  
crash

Expected Results:  
no crash

Using kmail 4.11.0-2 package on arch linux 64bit
Comment 1 Henri Valta 2013-08-31 08:28:29 UTC 
Created attachment 82052 [details]
The crash causing mail gzipped
Comment 2 Henri Valta 2013-08-31 08:29:10 UTC 
Created attachment 82053 [details]
Partial backtrace
Comment 3 Henri Valta 2013-08-31 08:53:09 UTC 
Turns out this is caused by fontconfig package upgrade to 2.10.94-1. Downgrading to 2.10.93-1 fixes the crash. Any message with chinese characters seems to cause the crash with 2.10.94-1

Is this a bug in fontconfig or kmail bug exposed by new fontconfig?
Comment 4 Henri Valta 2013-08-31 09:02:25 UTC 
Wow, thing are moving fast.
fontconfig update to 2.10.95-1 resolved the issue again and fontconfig changelog has this:
commit 272a99217b15e9cf1e4d2a1dcf92b540576c29a6
Author: Akira TAGOH <akira@tagoh.org>
Date:   Sat Aug 31 10:43:13 2013 +0900

    Fix a crash

So I think this should be just closed