Bug 197559

Summary: emptying kmail trash after index error
Product: [Unmaintained] kmail Reporter: Walter Mautner <retlaw.rentuam>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED INTENTIONAL    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Walter Mautner 2009-06-22 23:40:24 UTC
Application that crashed: kontact
Version of the application: 4.3.0 pre
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-9-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
After a "rebuild index" reoccuring error, trying to move messages in affected folder to trash worked but "empty trash" gave a crash

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fbc70cea00c in KMMsgDict::update (this=0x2185460, msg=0x26e9fa0, index=7, newIndex=6) at ../../kmail/folderstorage.h:592
#6  0x00007fbc70d5cfb3 in KMMsgList::remove (this=0x21c36a8, idx=<value optimized out>) at ../../kmail/kmmsglist.cpp:151
#7  0x00007fbc70d5d031 in KMMsgList::take (this=0x2185460, idx=7) at ../../kmail/kmmsglist.cpp:165
#8  0x00007fbc70cf222d in FolderStorage::removeMsg (this=0x21c3630, idx=3) at ../../kmail/folderstorage.cpp:397
#9  0x00007fbc70dc9c99 in KMFolderMaildir::removeMsg (this=0x21c3630, idx=3) at ../../kmail/kmfoldermaildir.cpp:893
#10 0x00007fbc70e8fa00 in KMMoveCommand::execute (this=0x27fc540) at ../../kmail/kmcommands.cpp:2129
#11 0x00007fbc70e75d7a in KMCommand::slotPostTransfer (this=0x27fc540, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:273
#12 0x00007fbc70e7fc53 in KMCommand::qt_metacall (this=0x27fc540, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5201f300) at ./kmcommands.moc:87
#13 0x00007fbc70e90ab0 in KMMoveCommand::qt_metacall (this=0x2185460, _c=40804256, _id=7, _a=0x6) at ./kmcommands.moc:1706
#14 0x00007fbc86aac74c in QMetaObject::activate (sender=0x27fc540, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x6) at kernel/qobject.cpp:3120
#15 0x00007fbc70e72f4e in KMCommand::messagesTransfered (this=0x2185460, _t1=KMCommand::OK) at ./kmcommands.moc:102
#16 0x00007fbc70e8e418 in KMCommand::transferSelectedMsgs (this=0x27fc540) at ../../kmail/kmcommands.cpp:367
#17 0x00007fbc70e8e63f in KMCommand::slotStart (this=0x27fc540) at ../../kmail/kmcommands.cpp:265
#18 0x00007fbc70e7fc36 in KMCommand::qt_metacall (this=0x27fc540, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5201f560) at ./kmcommands.moc:86
#19 0x00007fbc70e90ab0 in KMMoveCommand::qt_metacall (this=0x2185460, _c=40804256, _id=7, _a=0x6) at ./kmcommands.moc:1706
#20 0x00007fbc86aac74c in QMetaObject::activate (sender=0x27fc8b0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x6) at kernel/qobject.cpp:3120
#21 0x00007fbc86ab178f in QSingleShotTimer::timerEvent (this=0x27fc8b0) at kernel/qtimer.cpp:298
#22 0x00007fbc86aa6623 in QObject::event (this=0x27fc8b0, e=0x26e9fa0) at kernel/qobject.cpp:1082
#23 0x00007fbc873ae27c in QApplicationPrivate::notify_helper (this=0x1afdc20, receiver=0x27fc8b0, e=0x7fff5201fb70) at kernel/qapplication.cpp:4057
#24 0x00007fbc873b554e in QApplication::notify (this=0x7fff5201fed0, receiver=0x27fc8b0, e=0x7fff5201fb70) at kernel/qapplication.cpp:4022
#25 0x00007fbc8800bc16 in KApplication::notify (this=0x7fff5201fed0, receiver=0x27fc8b0, event=0x7fff5201fb70) at ../../kdeui/kernel/kapplication.cpp:302
#26 0x00007fbc86a9720c in QCoreApplication::notifyInternal (this=0x7fff5201fed0, receiver=0x27fc8b0, event=0x7fff5201fb70) at kernel/qcoreapplication.cpp:610
#27 0x00007fbc86ac2142 in QTimerInfoList::activateTimers (this=0x1b0a2f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#28 0x00007fbc86abfc1d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#29 0x00007fbc808ac8fe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0x00007fbc808affd8 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0x00007fbc808b0100 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0x00007fbc86abfb66 in QEventDispatcherGlib::processEvents (this=0x1ad2850, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#33 0x00007fbc8744255e in QGuiEventDispatcherGlib::processEvents (this=0x2185460, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00007fbc86a95b12 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#35 0x00007fbc86a95ee4 in QEventLoop::exec (this=0x7fff5201fe10, flags=) at kernel/qeventloop.cpp:200
#36 0x00007fbc86a97f89 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x0000000000403f27 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Walter Mautner 2009-09-09 21:09:29 UTC
resolved: I am using avira and dazukofs-3.0.0 which is not mmap-aware. Trying dazukofs-3.1.0rc2 (with patches) leads to gpf panic (another issue).

Therefore, I cannot use dazukofs/avira to monitor my home directory including the mail storage.