Bug 287953 - KMail crashed when trying to send an e-mail
Summary: KMail crashed when trying to send an e-mail
Status: RESOLVED DUPLICATE of bug 233574
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.6
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 288025 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-01 02:58 UTC by Joshua J. Kugler
Modified: 2011-12-04 10:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua J. Kugler 2011-12-01 02:58:50 UTC
Application: kmail (1.13.6)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-13-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
I had replied to an e-mail, and when I hit ctrl-enter to send the e-mail, the entire KMail application crashed.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77189b0 (LWP 1919))]

Thread 4 (Thread 0xb610eb70 (LWP 1932)):
#0  0x00d58416 in __kernel_vsyscall ()
#1  0x0091af76 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x0535e84b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0534e1af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x0534e92b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x03c28304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0x053772df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x082e7e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x0092973e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xb4cdcb70 (LWP 2123)):
#0  0x02b8ad41 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0x00aa0dd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x00b6d4f2 in updateCurrentTime (this=0xb3500524, tm=...) at kernel/qeventdispatcher_unix.cpp:339
#4  QTimerInfoList::timerWait (this=0xb3500524, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x00b6bd32 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb4cdc06c) at kernel/qeventdispatcher_glib.cpp:136
#6  0x00b6bdcd in timerSourcePrepare (source=0xb35004f0, timeout=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x0534cfd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x0534de63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0x0534e524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x00b6c577 in QEventDispatcherGlib::processEvents (this=0xa09ace8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0x00b3e289 in QEventLoop::processEvents (this=0xb4cdc220, flags=...) at kernel/qeventloop.cpp:149
#12 0x00b3e522 in QEventLoop::exec (this=0xb4cdc220, flags=...) at kernel/qeventloop.cpp:201
#13 0x00a482a0 in QThread::exec (this=0xa369998) at thread/qthread.cpp:492
#14 0x00b1ffdb in QInotifyFileSystemWatcherEngine::run (this=0xa369998) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x00a4ada2 in QThreadPrivate::start (arg=0xa369998) at thread/qthread_unix.cpp:320
#16 0x082e7e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0x0092973e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb6a9db70 (LWP 20131)):
#0  0x02b8ad41 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0x00aa0dd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x00b6d4f2 in updateCurrentTime (this=0xb35009cc, tm=...) at kernel/qeventdispatcher_unix.cpp:339
#4  QTimerInfoList::timerWait (this=0xb35009cc, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x00b6bd32 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb6a9d06c) at kernel/qeventdispatcher_glib.cpp:136
#6  0x00b6bdcd in timerSourcePrepare (source=0xb3500998, timeout=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x0534cfd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x0534de63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0x0534e524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x00b6c577 in QEventDispatcherGlib::processEvents (this=0xb35047c8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0x00b3e289 in QEventLoop::processEvents (this=0xb6a9d220, flags=...) at kernel/qeventloop.cpp:149
#12 0x00b3e522 in QEventLoop::exec (this=0xb6a9d220, flags=...) at kernel/qeventloop.cpp:201
#13 0x00a482a0 in QThread::exec (this=0xc45ec20) at thread/qthread.cpp:492
#14 0x00b1ffdb in QInotifyFileSystemWatcherEngine::run (this=0xc45ec20) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x00a4ada2 in QThreadPrivate::start (arg=0xc45ec20) at thread/qthread_unix.cpp:320
#16 0x082e7e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0x0092973e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb77189b0 (LWP 1919)):
[KCrash Handler]
#7  0x0112b82e in KMCommand::slotStart (this=0xcd16b50) at ../../kmail/kmcommands.cpp:265
#8  0x01132f2b in KMCommand::qt_metacall (this=0xcd16b50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x95c4ce0) at ./kmcommands.moc:92
#9  0x011337c2 in KMReplyToCommand::qt_metacall (this=0xcd16b50, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x95c4ce0) at ./kmcommands.moc:946
#10 0x00b456ba in QMetaObject::metacall (object=0xcd16b50, cl=QMetaObject::InvokeMetaMethod, idx=8, argv=0x95c4ce0) at kernel/qmetaobject.cpp:237
#11 0x00b4fe16 in QMetaCallEvent::placeMetaCall (this=0xb61add0, object=0xcd16b50) at kernel/qobject.cpp:535
#12 0x00b543b7 in QObject::event (this=0xcd16b50, e=0xb61add0) at kernel/qobject.cpp:1226
#13 0x075b9d24 in QApplicationPrivate::notify_helper (this=0x9224418, receiver=0xcd16b50, e=0xb61add0) at kernel/qapplication.cpp:4462
#14 0x075be8ce in QApplication::notify (this=0xbf99cb3c, receiver=0xcd16b50, e=0xb61add0) at kernel/qapplication.cpp:3862
#15 0x00596b9a in KApplication::notify (this=0xbf99cb3c, receiver=0xcd16b50, event=0xb61add0) at ../../kdeui/kernel/kapplication.cpp:311
#16 0x00b3f0bb in QCoreApplication::notifyInternal (this=0xbf99cb3c, receiver=0xcd16b50, event=0xb61add0) at kernel/qcoreapplication.cpp:731
#17 0x00b42c79 in sendEvent (receiver=0x0, event_type=0, data=0x91b7f28) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x91b7f28) at kernel/qcoreapplication.cpp:1372
#19 0x00b42e0d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1265
#20 0x00b6c3c4 in sendPostedEvents (s=0x9204310) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#21 postEventSourceDispatch (s=0x9204310) at kernel/qeventdispatcher_glib.cpp:277
#22 0x0534daa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#23 0x0534e270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#24 0x0534e524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#25 0x00b6c53c in QEventDispatcherGlib::processEvents (this=0x91b7a80, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#26 0x076701e5 in QGuiEventDispatcherGlib::processEvents (this=0x91b7a80, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00b3e289 in QEventLoop::processEvents (this=0xbf99ca04, flags=...) at kernel/qeventloop.cpp:149
#28 0x00b3e522 in QEventLoop::exec (this=0xbf99ca04, flags=...) at kernel/qeventloop.cpp:201
#29 0x00b42ecc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#30 0x075b78e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#31 0x0804a733 in main (argc=225909072, argv=0xca2db50) at ../../kmail/main.cpp:158

Possible duplicates by query: bug 212890.

Reported using DrKonqi
Comment 1 Joshua J. Kugler 2011-12-01 03:00:25 UTC
When I restarted KMail, the message was in the outbox, unsent. It sent OK.
Comment 2 Christophe Marin 2011-12-04 10:51:39 UTC
*** Bug 288025 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2011-12-04 10:52:32 UTC

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