Bug 208778 - KMail crash while reading email.
Summary: KMail crash while reading email.
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: disconnected IMAP (show other bugs)
Version: 1.12.1
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 167188 171630 214869 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-09-28 15:51 UTC by Matthew Dawson
Modified: 2011-12-27 04:10 UTC (History)
5 users (show)

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 Matthew Dawson 2009-09-28 15:51:25 UTC
Application that crashed: kmail
Version of the application: 1.12.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
While reading an html only email, I clicked on the link to enable the html output, kmail crashed.  It appears kmail crashed updating the status, however.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f98a07e3fdb in FolderStorage::setStatus (this=<value optimized out>, idx=248, status=..., toggle=false) at ../../kmail/folderstorage.cpp:1088
#6  0x00007f98a07e60a4 in FolderStorage::setStatus (this=0x13f7af0, ids=..., status=..., toggle=false) at ../../kmail/folderstorage.cpp:1098
#7  0x00007f98a089d03c in KMFolderCachedImap::setStatus (this=0x7f98a02a5aa0, ids=..., status=..., toggle=160) at ../../kmail/kmfoldercachedimap.cpp:1580
#8  0x00007f98a0976495 in KMSetStatusCommand::execute (this=0x2c6a790) at ../../kmail/kmcommands.cpp:1673
#9  0x00007f98a09701a2 in KMCommand::slotPostTransfer (this=0x2c6a790, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:274
#10 0x00007f98a0979f96 in KMCommand::qt_metacall (this=0x2c6a790, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff718db1c0) at ./kmcommands.moc:87
#11 0x00007f989ffc6682 in QMetaObject::activate (sender=0x2c6a790, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7f98a02a5aa0) at kernel/qobject.cpp:3112
#12 0x00007f98a096d45e in KMCommand::messagesTransfered (this=0x7f98a02a5aa0, _t1=KMCommand::OK) at ./kmcommands.moc:102
#13 0x00007f98a0988938 in KMCommand::transferSelectedMsgs (this=0x2c6a790) at ../../kmail/kmcommands.cpp:368
#14 0x00007f98a0988b56 in KMCommand::slotStart (this=0x2c6a790) at ../../kmail/kmcommands.cpp:266
#15 0x00007f98a0979faa in KMCommand::qt_metacall (this=0x2c6a790, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff718db3f0) at ./kmcommands.moc:86
#16 0x00007f989ffc6682 in QMetaObject::activate (sender=0x2afd6e0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7f98a02a5aa0) at kernel/qobject.cpp:3112
#17 0x00007f989ffcb7ef in QSingleShotTimer::timerEvent (this=0x2afd6e0) at kernel/qtimer.cpp:298
#18 0x00007f989ffc0bf3 in QObject::event (this=0x2afd6e0, e=0x2c6a7d8) at kernel/qobject.cpp:1074
#19 0x00007f989f42980d in QApplicationPrivate::notify_helper (this=0x1044240, receiver=0x2afd6e0, e=0x7fff718dbab0) at kernel/qapplication.cpp:4056
#20 0x00007f989f43186a in QApplication::notify (this=0x7fff718dbf10, receiver=0x2afd6e0, e=0x7fff718dbab0) at kernel/qapplication.cpp:4021
#21 0x00007f98a166643b in KApplication::notify (this=0x7fff718dbf10, receiver=0x2afd6e0, event=0x7fff718dbab0) at ../../kdeui/kernel/kapplication.cpp:302
#22 0x00007f989ffb151c in QCoreApplication::notifyInternal (this=0x7fff718dbf10, receiver=0x2afd6e0, event=0x7fff718dbab0) at kernel/qcoreapplication.cpp:610
#23 0x00007f989ffdd826 in QCoreApplication::sendEvent (this=0x1047b20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 QTimerInfoList::activateTimers (this=0x1047b20) at kernel/qeventdispatcher_unix.cpp:572
#25 0x00007f989ffd9c9d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#26 0x00007f989734a86a in g_main_dispatch (context=0x1046920) at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c:1824
#27 IA__g_main_context_dispatch (context=0x1046920) at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c:2377
#28 0x00007f989734deb8 in g_main_context_iterate (context=0x1046920, block=1, dispatch=1, self=<value optimized out>) at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c:2455
#29 0x00007f989734e06c in IA__g_main_context_iteration (context=0x1046920, may_block=1) at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c:2518
#30 0x00007f989ffd9bff in QEventDispatcherGlib::processEvents (this=0x1010170, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#31 0x00007f989f4c064f in QGuiEventDispatcherGlib::processEvents (this=0x7f98a02a5aa0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#32 0x00007f989ffafde2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007f989ffb01b4 in QEventLoop::exec (this=0x7fff718dbd60, flags=...) at kernel/qeventloop.cpp:201
#34 0x00007f989ffb2424 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#35 0x0000000000402fab in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-29 03:52:34 UTC
The backtrace seems related to bug 171630. Thanks
Comment 2 Christophe Marin 2009-10-23 10:02:27 UTC
*** Bug 171630 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2009-11-14 19:52:19 UTC
*** Bug 167188 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Marin 2009-11-16 21:39:42 UTC
*** Bug 214869 has been marked as a duplicate of this bug. ***
Comment 5 Matthew Dawson 2011-12-27 04:10:02 UTC
Since I've yet to reproduce this on any recent kmail version, and with kmail 2 completely redoing the whole stack (and probably fixing this bug), I'm marking it works for me for now.  If anyone else still has this issue on a recent version of kmail, feel free to reopen this bug.