Application: kmail (1.13.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.31-20-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
I recieved a mail (over IMAP) and responded to it by hitting 'a' to reply to all. Wrote my response and pressed Ctrl+Enter. The Application didn't respond at all (I thought) so I pressed the key combination again and then waited. The Compose message window greyed out and then the password dialog popped up to ask me for my password since I don't have my password saved so that will ask me every time. I entered my password (I would assume correctly) and pressed enter and the password dialog dissappeared followed by the compose window then by the main window. 
The KDE bug report assistant came up and asked if I would like to restart the Application or report the bug. I clicked on restart application and then report bug. A dialog box came up informing me that Kmail was already in session and I should not start it unless I was sure it was the only instance. I opened a process stats window and saw kmail running. I ran a kquitapp kwin and then proceeded to fill out this report.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0x0bd8b7c8 in ?? ()
#7  0x00dd91ab in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#8  0x00dd9522 in KMResendMessageCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#9  0x01342e5a in QMetaObject::metacall (object=0xb3e9cc8, cl=188368976, idx=8, argv=0xbf9b885c) at kernel/qmetaobject.cpp:237
#10 0x013515f5 in QMetaObject::activate (sender=0xb1f6cd0, m=0x1451188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#11 0x01359177 in QSingleShotTimer::timeout (this=0xb1f6cd0) at .moc/release-shared/qtimer.moc:82
#12 0x0135928c in QSingleShotTimer::timerEvent (this=0xb1f6cd0) at kernel/qtimer.cpp:308
#13 0x0134e494 in QObject::event (this=0xb1f6cd0, e=0xb1b8980) at kernel/qobject.cpp:1212
#14 0x0670d3cc in QApplicationPrivate::notify_helper (this=0x8f75d58, receiver=0xb1f6cd0, e=0xbf9b8d90) at kernel/qapplication.cpp:4300
#15 0x0671401e in QApplication::notify (this=0xbf9b91a0, receiver=0xb1f6cd0, e=0xbf9b8d90) at kernel/qapplication.cpp:3704
#16 0x002f05ba in KApplication::notify (this=0xbf9b91a0, receiver=0xb1f6cd0, event=0xbf9b8d90) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x0133dbeb in QCoreApplication::notifyInternal (this=0xbf9b91a0, receiver=0xb1f6cd0, event=0xbf9b8d90) at kernel/qcoreapplication.cpp:704
#18 0x0136ceb6 in QCoreApplication::sendEvent (this=0x8f81e94) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x8f81e94) at kernel/qeventdispatcher_unix.cpp:603
#20 0x01369b14 in timerSourceDispatch (source=0x8f81e60) at kernel/qeventdispatcher_glib.cpp:184
#21 0x01d59e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x01d5d730 in ?? () from /lib/libglib-2.0.so.0
#23 0x01d5d863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x01369805 in QEventDispatcherGlib::processEvents (this=0x8f4e270, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#25 0x067ccb35 in QGuiEventDispatcherGlib::processEvents (this=0x8f4e270, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x0133c209 in QEventLoop::processEvents (this=0xbf9b9054, flags=) at kernel/qeventloop.cpp:149
#27 0x0133c65a in QEventLoop::exec (this=0xbf9b9054, flags=...) at kernel/qeventloop.cpp:201
#28 0x0134084f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#29 0x0670d467 in QApplication::exec () at kernel/qapplication.cpp:3579
#30 0x0804aace in _start ()

Reported using DrKonqi