Bug 212856

Summary: kmail crashed when opening an attachment (in OpenOffice)
Product: [Unmaintained] kmail Reporter: Tim Richardson <tim>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tim Richardson 2009-11-03 03:41:51 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31-5.slh.2-sidux-686 i686
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
kmail crashed when double clicking on an attachment. the attachment was a spreadsheet in Excel format.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0xb5bbc941 in memcpy () from /lib/i686/cmov/libc.so.6
#7  0xb67b4628 in QByteArray::realloc (this=0x93876ec, alloc=4) at tools/qbytearray.cpp:1383
#8  0xb67b52de in QByteArray::operator= (this=0x93876ec, str=0xb7119420 "text") at tools/qbytearray.cpp:873
#9  0xb6c6c958 in KMMessagePart::clear (this=0x93876e4) at ../../kmail/kmmsgpart.cpp:66
#10 0xb6b45da4 in KMMessage::bodyPart (aDwBodyPart=0x1, aPart=0x93876e4, withBody=true) at ../../kmail/kmmessage.cpp:2712
#11 0xb6e1b4ea in partNode::msgPart (this=0xa410098) at ../../kmail/partNode.h:99
#12 KMHandleAttachmentCommand::slotStart (this=0xa410098) at ../../kmail/kmcommands.cpp:2913
#13 0xb6e09a0b in KMHandleAttachmentCommand::qt_metacall (this=0xa410098, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfdec138) at ./kmcommands.moc:2240
#14 0xb68b7303 in QMetaObject::activate (sender=0xa4290c0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#15 0xb68b7f42 in QMetaObject::activate (sender=0xa4290c0, m=0xb6992d88, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#16 0xb68bd007 in QSingleShotTimer::timeout (this=0xa4290c0) at .moc/release-shared/qtimer.moc:76
#17 0xb68bd12c in QSingleShotTimer::timerEvent (this=0xa4290c0) at kernel/qtimer.cpp:298
#18 0xb68b239f in QObject::event (this=0xa4290c0, e=0xbfdec5bc) at kernel/qobject.cpp:1074
#19 0xb5ee1a94 in QApplicationPrivate::notify_helper (this=0x9163490, receiver=0xa4290c0, e=0xbfdec5bc) at kernel/qapplication.cpp:4065
#20 0xb5ee9bee in QApplication::notify (this=0xbfdec8d8, receiver=0xa4290c0, e=0xbfdec5bc) at kernel/qapplication.cpp:3605
#21 0xb76470fd in KApplication::notify (this=0xbfdec8d8, receiver=0xa4290c0, event=0xbfdec5bc) at ../../kdeui/kernel/kapplication.cpp:302
#22 0xb68a21eb in QCoreApplication::notifyInternal (this=0xbfdec8d8, receiver=0xa4290c0, event=0xbfdec5bc) at kernel/qcoreapplication.cpp:610
#23 0xb68d0e21 in QCoreApplication::sendEvent (this=0x9166374) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 QTimerInfoList::activateTimers (this=0x9166374) at kernel/qeventdispatcher_unix.cpp:580
#25 0xb68cd317 in timerSourceDispatch (source=0x91663b0) at kernel/qeventdispatcher_glib.cpp:184
#26 idleTimerSourceDispatch (source=0x91663b0) at kernel/qeventdispatcher_glib.cpp:231
#27 0xb3ff2e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#28 0xb3ff6623 in ?? () from /lib/libglib-2.0.so.0
#29 0xb3ff67a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#30 0xb68cd041 in QEventDispatcherGlib::processEvents (this=0x913c900, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#31 0xb5f81305 in QGuiEventDispatcherGlib::processEvents (this=0x913c900, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#32 0xb68a083a in QEventLoop::processEvents (this=0xbfdec7e0, flags=...) at kernel/qeventloop.cpp:149
#33 0xb68a0c82 in QEventLoop::exec (this=0xbfdec7e0, flags=...) at kernel/qeventloop.cpp:201
#34 0xb68a30d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#35 0xb5ee1917 in QApplication::exec () at kernel/qapplication.cpp:3525
#36 0x0804a6d0 in main (argc=) at ../../kmail/main.cpp:146

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

Reported using DrKonqi
Comment 1 Christophe Marin 2009-11-03 11:16:57 UTC

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