Bug 170396

Summary: Kmail crashes when it opens
Product: [Applications] kontact Reporter: dc
Component: mailAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: File containing the mail crashing kmail

Description dc 2008-09-04 17:35:11 UTC
Version:           unknown (using 4.1.1 (KDE 4.1.1), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-21-generic

Kmail crashes while it tries to open a mail containing some bizarre MIME/parts (probably calendar) and/or MS* sh...

Here is the dump :

Application: Kontact (kontact), signal SIGSEGV
(no debugging symbols found)                  
[Thread debugging using libthread_db enabled] 
[New Thread 0xb5571940 (LWP 6806)]            
[New Thread 0xb1caeb90 (LWP 7324)]            
(no debugging symbols found)                  
[KCrash handler]                              
#6  0xb5ede2d7 in KCal::Incidence::revision ()
   from /usr/lib/kde4/lib/libkcal.so.4        
#7  0xb5f32994 in KCal::IncidenceFormatter::formatICalInvitation ()
   from /usr/lib/kde4/lib/libkcal.so.4                             
#8  0xb1cb7f2b in ?? ()                                            
   from /usr/lib/kde4/lib/kde4/kmail_bodypartformatter_text_calendar.so
#9  0xb256fa10 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#10 0xb256fd06 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#11 0xb256ff8c in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#12 0xb257c37b in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#13 0xb256fb99 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#14 0xb256fd06 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#15 0xb256fff6 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#16 0xb257c43b in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#17 0xb256fb99 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#18 0xb243bd72 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#19 0xb2432cd9 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#20 0xb2432eae in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#21 0xb2436690 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4    
#22 0xb78bcf79 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb78bd642 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb78fa817 in QTimer::timeout () from /usr/lib/libQtCore.so.4      
#25 0xb78c40fe in QTimer::timerEvent () from /usr/lib/libQtCore.so.4   
#26 0xb78b79fa in QObject::event () from /usr/lib/libQtCore.so.4
#27 0xb6f6ef9c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#28 0xb6f73bf9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#29 0xb7d441c3 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#30 0xb78a80b9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#31 0xb78d5c01 in ?? () from /usr/lib/libQtCore.so.4
#32 0xb78d34a0 in ?? () from /usr/lib/libQtCore.so.4
#33 0xb5b11dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0xb5b15193 in ?? () from /usr/lib/libglib-2.0.so.0
#35 0xb5b1574e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0xb78d39f8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#37 0xb7002a25 in ?? () from /usr/lib/libQtGui.so.4
#38 0xb78a733d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#39 0xb78a74cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#40 0xb78a974d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#41 0xb6f6e897 in QApplication::exec () from /usr/lib/libQtGui.so.4
#42 0x0804b326 in _start ()
#0  0xb7ffb410 in __kernel_vsyscall ()

I also include the (supposedly) faulty mail.

dc
Comment 1 dc 2008-09-04 17:38:30 UTC
Created attachment 27240 [details]
File containing the mail crashing kmail
Comment 2 Thomas McGuire 2008-09-05 15:45:25 UTC

*** This bug has been marked as a duplicate of bug 170203 ***