Application: kmail (1.13.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2) "release 231"
Qt Version: 4.6.2
Operating System: Linux 2.6.31.12-0.2-desktop i686
Distribution: "openSUSE 11.2 (i586)"

-- Information about the crash:
Kmail crashes when clicking on the attachment listing in an email header section before the body has completely loaded.  

The file listing in the header seems to be a 'link' to the attachment in the body of the email, thus opening the file when the link is clicked.

The problem seems to be that when the link in the header section is clicked during the time-frame before the body has completely loaded (I access my Gmail via IMAP) , the attachment has not yet displayed in the body of the email, Kmail then crashes obviously while trying to access that attachment that should be there, but has not loaded into memory.  This happens everytime regardless of the size or type of attachment.

If the link to the attachment in the header is clicked after the whole body has loaded, the file is downloaded and opened without any problem.

This has been confirmed in KDE 4.4.2 and 4.3.5, and only in 32-bit but I have not tested this in 64-bit.

The crash can be reproduced every time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  operator!= (value=<value optimized out>, this=<value optimized out>) at ../../src/corelib/thread/qbasicatomic.h:75
#7  QByteArray::operator= (value=<value optimized out>, this=<value optimized out>) at tools/qbytearray.cpp:887
#8  0xb6b6bb08 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb6a47073 in GpgME::Signature::summary() const () from /usr/lib/libkmailprivate.so.4
#10 0xb6d18a41 in KMHandleAttachmentCommand::slotStart() () from /usr/lib/libkmailprivate.so.4
#11 0xb6d1affc in KMHandleAttachmentCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#12 0xb66f814d in QMetaObject::metacall (object=0x8812620, cl=1819488512, idx=14, argv=0xbfc2219c) at kernel/qmetaobject.cpp:237
#13 0xb6706faa in QMetaObject::activate (sender=0x86d6b58, m=0xb6808188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#14 0xb670ec95 in QSingleShotTimer::timeout (this=0x86d6b58) at .moc/release-shared/qtimer.moc:82
#15 0xb670edcc in QSingleShotTimer::timerEvent (this=0x86d6b58) at kernel/qtimer.cpp:308
#16 0xb6703ab4 in QObject::event (this=0x86d6b58, e=0x4) at kernel/qobject.cpp:1212
#17 0xb5c1a3fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb5c21248 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb751ec01 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0xb66f2dde in QCoreApplication::notifyInternal (this=0xbfc22af0, receiver=0x86d6b58, event=0xbfc226f4) at kernel/qcoreapplication.cpp:704
#21 0xb6722ffe in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#22 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617
#23 0xb671fc62 in timerSourceDispatch (source=0x8087f08) at kernel/qeventdispatcher_glib.cpp:184
#24 0xb3d894c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb3d8cd98 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb3d8cebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb671f931 in QEventDispatcherGlib::processEvents (this=0x8055f18, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#28 0xb5cdae0a in ?? () from /usr/lib/libQtGui.so.4
#29 0xb66f144d in QEventLoop::processEvents (this=0xbfc229a4, flags=) at kernel/qeventloop.cpp:149
#30 0xb66f1899 in QEventLoop::exec (this=0xbfc229a4, flags=...) at kernel/qeventloop.cpp:201
#31 0xb66f5a10 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0xb5c1a4a4 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#33 0x0804ab1e in _start ()

Reported using DrKonqi