Bug 216913

Summary: crash when trying to forward a specific mail via shortcut (F)
Product: [Applications] kontact Reporter: Arne Babenhauserheide <arne_bab>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, moabi2000
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:

Description Arne Babenhauserheide 2009-12-01 10:40:52 UTC
Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64

What I was doing when the application crashed:
When I tried to forward an email (account activation info from the flipside forums) Kontact crashed. 

A second try (after restart) had the same result, so I assume I can reproduce it. 

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KMReaderWin::htmlMail (this=0x0) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:2558
#6  0x00007f30fbde7ee7 in KMail::ObjectTreeParser::processMultiPartAlternativeSubtype (this=0x7fff9d22b540, node=<value optimized out>)
    at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/objecttreeparser.cpp:1182
#7  0x00007f30fbde7ae0 in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff9d22b540, node=0x2944300) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/objecttreeparser.cpp:296
#8  0x00007f30fbc24476 in KMMessage::parseTextStringFromDwPart (this=<value optimized out>, root=0x2944300, parsedString=@0x7fff9d22b760, codec=@0x7fff9d22b758, isHTML=@0x7fff9d22b76f)
    at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmmessage.cpp:502
#9  0x00007f30fbc246a8 in KMMessage::asPlainText (this=0x28f6d80, aStripSignature=false, allowDecryption=false) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmmessage.cpp:527
#10 0x00007f30fbc26ae1 in KMMessage::createForward (this=0x28f6d80, tmpl=@0x7fff9d22bda0) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmmessage.cpp:1001
#11 0x00007f30fbe0806d in KMForwardCommand::execute (this=0x2598e50) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:1344
#12 0x00007f30fbe0cd1b in KMCommand::slotPostTransfer (this=0x2598e50, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:274
#13 0x00007f30fbe0cdf6 in KMCommand::qt_metacall (this=0x2598e50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff9d22c390)
    at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmcommands.moc:87
#14 0x00007f310d765e69 in QMetaObject::activate (sender=0x2598e50, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101
#15 0x00007f30fbdf7a3e in KMCommand::messagesTransfered (this=0x0, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmcommands.moc:102
#16 0x00007f30fbe0cb2b in KMCommand::transferSelectedMsgs (this=0x2598e50) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:368
#17 0x00007f30fbe0d7de in KMCommand::slotStart (this=0x2598e50) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:266
#18 0x00007f30fbe0ce0a in KMCommand::qt_metacall (this=0x2598e50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff9d22c610)
    at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmcommands.moc:86
#19 0x00007f310d765e69 in QMetaObject::activate (sender=0x1803760, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101
#20 0x00007f310d76b5ff in QSingleShotTimer::timerEvent (this=0x1803760) at kernel/qtimer.cpp:298
#21 0x00007f310d760763 in QObject::event (this=0x1803760, e=0x3) at kernel/qobject.cpp:1066
#22 0x00007f310e4f46dd in QApplicationPrivate::notify_helper (this=0x63c2f0, receiver=0x1803760, e=0x7fff9d22ccf0) at kernel/qapplication.cpp:4065
#23 0x00007f310e4fd00e in QApplication::notify (this=0x7fff9d22d030, receiver=0x1803760, e=0x7fff9d22ccf0) at kernel/qapplication.cpp:4030
#24 0x00007f310f2c30f1 in KApplication::notify (this=0x7fff9d22d030, receiver=0x1803760, event=0x7fff9d22ccf0)
    at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#25 0x00007f310d750d03 in QCoreApplication::notifyInternal (this=0x7fff9d22d030, receiver=0x1803760, event=0x7fff9d22ccf0) at kernel/qcoreapplication.cpp:606
#26 0x00007f310d77abd6 in QTimerInfoList::activateTimers (this=0x64c220) at kernel/qcoreapplication.h:213
#27 0x00007f310d777e2d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#28 0x00007f3108d33fc1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0x00007f3108d37558 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#30 0x00007f3108d3770c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0x00007f310d777d9f in QEventDispatcherGlib::processEvents (this=0x63bbb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#32 0x00007f310e58028f in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#33 0x00007f310d74f9c2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1658663072}) at kernel/qeventloop.cpp:149
#34 0x00007f310d74fb5c in QEventLoop::exec (this=0x7fff9d22cfa0, flags={i = -1658662992}) at kernel/qeventloop.cpp:197
#35 0x00007f310d7544d6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#36 0x000000000040405a in main (argc=1, argv=0x7fff9d22d548) at /var/tmp/portage/kde-base/kontact-4.3.3/work/kontact-4.3.3/kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 214436

Reported using DrKonqi
Comment 1 FiNeX 2009-12-01 17:43:41 UTC
*** Bug 216920 has been marked as a duplicate of this bug. ***
Comment 2 Dario Andres 2009-12-06 20:49:08 UTC
Fixed in KDE SC 4.3.4 and 4.4+ Thanks

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