Application: kmail (2.0.89) KDE Platform Version: 4.5.67 (4.6 >= 20100901) Qt Version: 4.7.0 Operating System: Linux 2.6.35.4-desktop-1mnb x86_64 Distribution: "Mandriva Linux 2010.1" -- Information about the crash: - What I was doing when the application crashed: I looked at new unread message (I have reading pane so message is automatically shown) and got pop-up that I never saw before - something about message time and flags, apparently it believed some attributes were conflicting. I clicked on "Keep both" and KMail crashed. -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7f5a5f666720 (LWP 11475))] Thread 2 (Thread 0x7f5a4239d710 (LWP 11479)): #0 0x00007f5a5afe60bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f5a527438d4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #2 0x00007f5a5afe1a5d in start_thread () from /lib64/libpthread.so.0 #3 0x00007f5a5c98115d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f5a5f666720 (LWP 11475)): [KCrash Handler] #6 0x00007f5a5c8d7925 in raise () from /lib64/libc.so.6 #7 0x00007f5a5c8d8f40 in abort () from /lib64/libc.so.6 #8 0x00007f5a5d1985d4 in qt_message_output (msgType=<value optimized out>, buf=<value optimized out>) at global/qglobal.cpp:2259 #9 0x00007f5a5d19879d in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7f5a5d2e8d88 "ASSERT: \"%s\" in file %s, line %d", ap=0x7fffe692dfa0) at global/qglobal.cpp:2305 #10 0x00007f5a5d198935 in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2488 #11 0x00007f5a595045b2 in Akonadi::ItemCreateJob::ItemCreateJob (this=0x385dd30, item=..., collection=..., parent=<value optimized out>) at /usr/src/debug/kdepimlibs-4.5.67svn1170578/akonadi/itemcreatejob.cpp:57 #12 0x00007f5a594d5af2 in Akonadi::ConflictHandler::useBothItems (this=0x32cb890) at /usr/src/debug/kdepimlibs-4.5.67svn1170578/akonadi/conflicthandling/conflicthandler.cpp:128 #13 0x00007f5a594d5bd8 in Akonadi::ConflictHandler::resolve (this=0x32cb890) at /usr/src/debug/kdepimlibs-4.5.67svn1170578/akonadi/conflicthandling/conflicthandler.cpp:91 #14 0x00007f5a594d624c in Akonadi::ConflictHandler::qt_metacall (this=0x32cb890, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x32d9250) at /usr/src/debug/kdepimlibs-4.5.67svn1170578/build/akonadi/conflicthandler_p.moc:91 #15 0x00007f5a5d29daba in QObject::event (this=0x32cb890, e=<value optimized out>) at kernel/qobject.cpp:1211 #16 0x00007f5a5d7726e4 in QApplicationPrivate::notify_helper (this=0x1123dd0, receiver=0x32cb890, e=0x31af7f0) at kernel/qapplication.cpp:4396 #17 0x00007f5a5d77715a in QApplication::notify (this=<value optimized out>, receiver=0x32cb890, e=0x31af7f0) at kernel/qapplication.cpp:4277 #18 0x00007f5a5f039c86 in KApplication::notify (this=0x7fffe692ec90, receiver=0x32cb890, event=0x31af7f0) at /usr/src/debug/kdelibs-4.5.67svn1170578/kdeui/kernel/kapplication.cpp:310 #19 0x00007f5a5d28973c in QCoreApplication::notifyInternal (this=0x7fffe692ec90, receiver=0x32cb890, event=0x31af7f0) at kernel/qcoreapplication.cpp:732 #20 0x00007f5a5d28cee5 in sendEvent (receiver=0x0, event_type=0, data=0x10dcd30) at kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x10dcd30) at kernel/qcoreapplication.cpp:1373 #22 0x00007f5a5d2b46c3 in sendPostedEvents (s=0x1126990) at kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=0x1126990) at kernel/qeventdispatcher_glib.cpp:277 #24 0x00007f5a553203d3 in g_main_dispatch (context=0x11268b0) at gmain.c:2119 #25 g_main_context_dispatch (context=0x11268b0) at gmain.c:2672 #26 0x00007f5a55320bb0 in g_main_context_iterate (context=0x11268b0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2750 #27 0x00007f5a55320e4d in g_main_context_iteration (context=0x11268b0, may_block=1) at gmain.c:2813 #28 0x00007f5a5d2b485f in QEventDispatcherGlib::processEvents (this=0x10dc4b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415 #29 0x00007f5a5d81674e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #30 0x00007f5a5d288ad2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #31 0x00007f5a5d288d1c in QEventLoop::exec (this=0x7fffe692eb30, flags=...) at kernel/qeventloop.cpp:201 #32 0x00007f5a5d28d19b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #33 0x0000000000402e66 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.5.67svn1170578/kmail/main.cpp:145 Reported using DrKonqi
Created attachment 52184 [details] New crash information added by DrKonqi kmail (2.0.89) on KDE Platform 4.5.68 (4.6 >= 20100912) using Qt 4.7.0 - What I was doing when the application crashed: While IMAP syncing was running, I was shown a cryptic KMail dialog that only contained the following text: Modification Time: 00:00:00 02.10.2010 22:33:38 The two fields had red background color. I was given options to "Take left one", "Take right one", or "Keep both". I selected "Keep both" and kmail crashed. -- Backtrace (Reduced): #11 0x00007f38c6fdea52 in Akonadi::ItemCreateJob::ItemCreateJob (this=0x542f290, item=..., collection=..., parent=<value optimized out>) at /usr/src/debug/kdepimlibs-4.5.68svn1174542/akonadi/itemcreatejob.cpp:57 #12 0x00007f38c6fb02f2 in Akonadi::ConflictHandler::useBothItems (this=0x328f500) at /usr/src/debug/kdepimlibs-4.5.68svn1174542/akonadi/conflicthandling/conflicthandler.cpp:128 #13 0x00007f38c6fb03d8 in Akonadi::ConflictHandler::resolve (this=0x328f500) at /usr/src/debug/kdepimlibs-4.5.68svn1174542/akonadi/conflicthandling/conflicthandler.cpp:91 #14 0x00007f38c6fb0a4c in Akonadi::ConflictHandler::qt_metacall (this=0x328f500, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xe1ef560) at /usr/src/debug/kdepimlibs-4.5.68svn1174542/build/akonadi/conflicthandler_p.moc:91 #15 0x00007f38cad84aba in QObject::event (this=0x328f500, e=<value optimized out>) at kernel/qobject.cpp:1211
[Comment from a bug triager] From bug 253695: -- Information about the crash: I viewing and deleting messages from local mailbox. After some manipulations ?dialog show(I dont remember its caption) and I press "Keep both" button. From bug 250980: - What I was doing when the application crashed: I was marking all messages in a folder as all read. It was called "Heb-Bugzap" and had twenty unread messages. This is on Mandriva Linux Cooker with kmail2 and kdepimlib compiled from the trunk.
*** Bug 253695 has been marked as a duplicate of this bug. ***
*** Bug 250980 has been marked as a duplicate of this bug. ***
*** Bug 252277 has been marked as a duplicate of this bug. ***
*** Bug 268647 has been marked as a duplicate of this bug. ***
*** Bug 276751 has been marked as a duplicate of this bug. ***
*** Bug 258204 has been marked as a duplicate of this bug. ***
*** Bug 277860 has been marked as a duplicate of this bug. ***
Created attachment 61941 [details] New crash information added by DrKonqi kontact (4.7 rc2) on KDE Platform 4.6.95 (4.7 RC2) "release 1" using Qt 4.7.3 - What I was doing when the application crashed: While the computer was under heavy load I navigated to another folder witzhin kmail shich took ages, a conflict warning came up, I picked the right version and then it crashed. -- Backtrace (Reduced): #6 isSignalConnected (sender=0x3dc0590, m=<value optimized out>, local_signal_index=0, argv=0x0) at kernel/qobject_p.h:221 [...] #8 0x00007f2e0b772938 in useOtherItem (this=0x3dc0590) at /usr/src/debug/kdepimlibs-4.6.95/akonadi/conflicthandling/conflicthandler.cpp:121 #9 Akonadi::ConflictHandler::resolve (this=0x3dc0590) at /usr/src/debug/kdepimlibs-4.6.95/akonadi/conflicthandling/conflicthandler.cpp:88 #10 0x00007f2e0b772a7c in Akonadi::ConflictHandler::qt_metacall (this=0x3dc0590, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x60952f0) at /usr/src/debug/kdepimlibs-4.6.95/build/akonadi/conflicthandler_p.moc:91 #11 0x00007f2e0f8d637a in QObject::event (this=0x3dc0590, e=<value optimized out>) at kernel/qobject.cpp:1217
*** Bug 279179 has been marked as a duplicate of this bug. ***
*** Bug 285883 has been marked as a duplicate of this bug. ***
*** Bug 288348 has been marked as a duplicate of this bug. ***
*** Bug 289731 has been marked as a duplicate of this bug. ***
*** Bug 294228 has been marked as a duplicate of this bug. ***
Created attachment 69792 [details] New crash information added by DrKonqi kontact (4.7.3) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4 - What I was doing when the application crashed: Closing Kontact. Kontact was causing HUGE delays. So far, it appears my problems are with the Filtering subsystem, likely due to the change in how KMail refers to folders internally. In KMail1, these were actual paths, in KMail2 they are now just a number. I'm also seeing messages about "Append Failed" and "NO Mailbox does not exist" (a Cyrus error message). If I manually change the kmail2rc file to have 0 filters, things seem fine: [General] filters=0 As soon as I run the AntiSpam Wizard again all the problems begin again. -- Backtrace (Reduced): #6 operator!= (value=1, this=0x65674165726978) at /usr/include/qt4/QtCore/qbasicatomic.h:75 [...] #8 operator-> (this=0x42e9980) at /usr/include/qt4/QtCore/qshareddata.h:78 #9 Akonadi::Entity::parentCollection (this=<optimized out>) at ../../akonadi/entity.cpp:177 #10 0x00007ff398454d6f in Akonadi::ConflictHandler::useBothItems (this=0x42e9960) at ../../akonadi/conflicthandling/conflicthandler.cpp:128 #11 0x00007ff398454e98 in Akonadi::ConflictHandler::resolve (this=0x42e9960) at ../../akonadi/conflicthandling/conflicthandler.cpp:91
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.