Bug 237633 - KMail2 crashes when changing folders using IMAP account
Summary: KMail2 crashes when changing folders using IMAP account
Status: VERIFIED DUPLICATE of bug 233397
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 1.99.0
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: akonadi-ports-regression
Depends on:
Blocks: 223438
  Show dependency treegraph
 
Reported: 2010-05-14 16:24 UTC by Artur Souza (MoRpHeUz)
Modified: 2010-07-05 00:18 UTC (History)
3 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 Artur Souza (MoRpHeUz) 2010-05-14 16:24:30 UTC
Application: kmail (1.99.0)
KDE Platform Version: 4.4.75 (KDE 4.4.75 (KDE 4.5 >= 20100505)) (Compiled from sources)
Qt Version: 4.7.0
Operating System: Linux 2.6.33.3-custom i686

-- Information about the crash:
- What I was doing when the application crashed:

Checking my email and changing from one folder to another. I changed from one folder to another clicking on the name of the folders.

- Unusual behavior I noticed:

After crashing, the output in konsole was:

kmail(1392) KMMoveCommand::execute: AKONADI PORT: Disabled code in   virtual KMCommand::Result KMMoveCommand::execute()
kmail(1392) KMMainWidget::updateMessageActions: Fix enable/disable send_queued action 
kmail(1392) KMReaderWin::setMessage: void KMReaderWin::setMessage(const Akonadi::Item&, MessageViewer::Viewer::UpdateMode) QSplitter(0x8ca1bb0, name = "splitter2")
kmail(1392) MessageList::StorageModel::messageForRow: Not a message -1 "" "" 
ASSERT: "mail" in file /usr/local/kde4/src/KDE/kdepim/messagelist/storagemodel.cpp, line 292
*** KMail got signal 6 (Crashing)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmail path = /usr/local/kde4/bin pid = 1392
KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/morphbr/.kde4/socket-wakko/kdeinit4__0


Also the process stays there and I need to kill "by hand" in order to be able to start KMail2 again.

- Custom settings of the application:

IMAP account using GMail

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[Current thread is 1 (Thread 0xb19bf710 (LWP 10825))]

Thread 2 (Thread 0xaf41cb70 (LWP 10831)):
#0  0xb4e3c000 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0xb3a125b2 in WTF::TCMalloc_PageHeap::scavengerThread() () from /home/morphbr/install/qt-4.7/lib/libQtWebKit.so.4
#2  0xb3a11d12 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /home/morphbr/install/qt-4.7/lib/libQtWebKit.so.4
#3  0xb4e379a0 in start_thread () from /lib/libpthread.so.0
#4  0xb4c800de in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb19bf710 (LWP 10825)):
[KCrash Handler]
#6  0xb4bcd8f7 in raise () from /lib/libc.so.6
#7  0xb4bcf162 in abort () from /lib/libc.so.6
#8  0xb4ee389e in qt_message_output (msgType=QtFatalMsg, buf=0xa957df8 "ASSERT: \"mModelForItemFunctions\" in file /usr/local/kde4/src/KDE/kdepim/messagelist/core/model.cpp, line 2916")
    at /work/projects/qt/src/corelib/global/qglobal.cpp:2271
#9  0xb4ee3a66 in qt_message (msgType=QtFatalMsg, msg=0xb509822c "ASSERT: \"%s\" in file %s, line %d", ap=0xbfaff644 "\225\071\202\264H7\202\264d\v")
    at /work/projects/qt/src/corelib/global/qglobal.cpp:2317
#10 0xb4ee3ebf in qFatal (msg=0xb509822c "ASSERT: \"%s\" in file %s, line %d") at /work/projects/qt/src/corelib/global/qglobal.cpp:2500
#11 0xb4ee33ff in qt_assert (assertion=0xb4823995 "mModelForItemFunctions", file=0xb4823748 "/usr/local/kde4/src/KDE/kdepim/messagelist/core/model.cpp", line=2916)
    at /work/projects/qt/src/corelib/global/qglobal.cpp:2016
#12 0xb47b03d6 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Cleanup (this=0x97c27e8, job=0xa7dab38, tStart=...)
    at /usr/local/kde4/src/KDE/kdepim/messagelist/core/model.cpp:2916
#13 0xb47b1710 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJob (this=0x97c27e8, job=0xa7dab38, tStart=...) at /usr/local/kde4/src/KDE/kdepim/messagelist/core/model.cpp:3362
#14 0xb47b1f34 in MessageList::Core::ModelPrivate::viewItemJobStepInternal (this=0x97c27e8) at /usr/local/kde4/src/KDE/kdepim/messagelist/core/model.cpp:3718
#15 0xb47b2864 in MessageList::Core::ModelPrivate::viewItemJobStep (this=0x97c27e8) at /usr/local/kde4/src/KDE/kdepim/messagelist/core/model.cpp:3933
#16 0xb47b485e in MessageList::Core::Model::qt_metacall (this=0x97ef670, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfaffa2c) at /usr/local/kde4/build/KDE/kdepim/messagelist/model.moc:90
#17 0xb50198c2 in QMetaObject::metacall (object=0x97ef670, cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0xbfaffa2c) at /work/projects/qt/src/corelib/kernel/qmetaobject.cpp:237
#18 0xb502f1e2 in QMetaObject::activate (sender=0x97c2804, m=0xb51a07a4, local_signal_index=0, argv=0x0) at /work/projects/qt/src/corelib/kernel/qobject.cpp:3272
#19 0xb50947fd in QTimer::timeout (this=0x97c2804) at .moc/debug-shared/moc_qtimer.cpp:134
#20 0xb50382e5 in QTimer::timerEvent (this=0x97c2804, e=0xbfaffff4) at /work/projects/qt/src/corelib/kernel/qtimer.cpp:271
#21 0xb502b190 in QObject::event (this=0x97c2804, e=0xbfaffff4) at /work/projects/qt/src/corelib/kernel/qobject.cpp:1175
#22 0xb572d203 in QApplicationPrivate::notify_helper (this=0x955eff0, receiver=0x97c2804, e=0xbfaffff4) at /work/projects/qt/src/gui/kernel/qapplication.cpp:4341
#23 0xb572a94c in QApplication::notify (this=0xbfb00388, receiver=0x97c2804, e=0xbfaffff4) at /work/projects/qt/src/gui/kernel/qapplication.cpp:3745
#24 0xb750efbe in KApplication::notify (this=0xbfb00388, receiver=0x97c2804, event=0xbfaffff4) at /usr/local/kde4/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:302
#25 0xb5011830 in QCoreApplication::notifyInternal (this=0xbfb00388, receiver=0x97c2804, event=0xbfaffff4) at /work/projects/qt/src/corelib/kernel/qcoreapplication.cpp:719
#26 0xb571c4a6 in QCoreApplication::sendEvent (receiver=0x97c2804, event=0xbfaffff4) at ../../include/QtCore/../../../../qt/src/corelib/kernel/qcoreapplication.h:215
#27 0xb504f855 in QTimerInfoList::activateTimers (this=0x9561e34) at /work/projects/qt/src/corelib/kernel/qeventdispatcher_unix.cpp:602
#28 0xb504b1e5 in timerSourceDispatch (source=0x9561e00) at /work/projects/qt/src/corelib/kernel/qeventdispatcher_glib.cpp:184
#29 0xb27dd0f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb27e0990 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb27e0ac3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb504c4ad in QEventDispatcherGlib::processEvents (this=0x9554960, flags=...) at /work/projects/qt/src/corelib/kernel/qeventdispatcher_glib.cpp:412
#33 0xb5808f63 in QGuiEventDispatcherGlib::processEvents (this=0x9554960, flags=...) at /work/projects/qt/src/gui/kernel/qguieventdispatcher_glib.cpp:204
#34 0xb500ea2a in QEventLoop::processEvents (this=0xbfb002bc, flags=...) at /work/projects/qt/src/corelib/kernel/qeventloop.cpp:149
#35 0xb500eb5f in QEventLoop::exec (this=0xbfb002bc, flags=...) at /work/projects/qt/src/corelib/kernel/qeventloop.cpp:201
#36 0xb5011f33 in QCoreApplication::exec () at /work/projects/qt/src/corelib/kernel/qcoreapplication.cpp:996
#37 0xb572a53f in QApplication::exec () at /work/projects/qt/src/gui/kernel/qapplication.cpp:3620
#38 0x0804afdd in main (argc=1, argv=0xbfb00494) at /usr/local/kde4/src/KDE/kdepim/kmail/main.cpp:147

Reported using DrKonqi
Comment 1 Casey Link 2010-05-26 03:23:15 UTC
Is this reproducible?
Comment 2 Artur Souza (MoRpHeUz) 2010-05-26 14:41:16 UTC
I can easily reproduce just clicking in different folders. I'll try with today's (26/05/2010) trunk again.

Cheers,
Comment 3 Thomas McGuire 2010-05-27 19:16:12 UTC

*** This bug has been marked as a duplicate of bug 233397 ***
Comment 4 Sabine Faure 2010-07-05 00:18:49 UTC
I tested this today and it works fine now.

Trunk, Svn Rev 1145265