Application: kmail (1.13.5) KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2" Qt Version: 4.6.3 Operating System: Linux 2.6.34.4-0.1-default i686 Distribution: "openSUSE 11.3 (i586)" -- Information about the crash: Kmail and Kontact both programs crash right after startup The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 begin (this=0x84725f8, msg=0x86e5ad8, subjects=..., predicatesArray=..., valuesArray=...) at /usr/include/QtCore/qlist.h:93 #7 constBegin (this=0x84725f8, msg=0x86e5ad8, subjects=..., predicatesArray=..., valuesArray=...) at /usr/include/QtCore/qlist.h:250 #8 KMail::MailManagerImpl::processMsgBase (this=0x84725f8, msg=0x86e5ad8, subjects=..., predicatesArray=..., valuesArray=...) at /usr/src/debug/kdepim-4.4.4/kmail/mailmanagerimpl.cpp:86 #9 0xb6f63fab in KMail::MailManagerImpl::Register (this=0x84725f8, registrarPath=..., lastModseq=1284377940) at /usr/src/debug/kdepim-4.4.4/kmail/mailmanagerimpl.cpp:166 #10 0xb705ddc1 in ManagerAdaptor::Register (this=0x8472f90, registrar_path=..., last_modseq=1284377940) at /usr/src/debug/kdepim-4.4.4/build/kmail/manageradaptor.cpp:39 #11 0xb705de3e in ManagerAdaptor::qt_metacall (this=0x8472f90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfd4092c) at /usr/src/debug/kdepim-4.4.4/build/kmail/manageradaptor.moc:83 #12 0xb5831a37 in QDBusConnectionPrivate::deliverCall (this=0x807a378, object=0x8472f90, msg=..., metaTypes=..., slotIdx=0) at qdbusintegrator.cpp:904 #13 0xb5833be7 in QDBusConnectionPrivate::activateCall (this=0x807a378, object=0x8472f90, flags=273, msg=...) at qdbusintegrator.cpp:809 #14 0xb5834378 in QDBusConnectionPrivate::activateObject (this=0x807a378, node=..., msg=..., pathStartPos=138881000) at qdbusintegrator.cpp:1383 #15 0xb5834878 in QDBusActivateObjectEvent::placeMetaCall (this=0x86e3c98) at qdbusintegrator.cpp:1477 #16 0xb691993f in QObject::event (this=0x84725f8, e=0x86e3c98) at kernel/qobject.cpp:1248 #17 0xb5e5bc64 in QApplicationPrivate::notify_helper (this=0x8083a48, receiver=0x84725f8, e=0x86e3c98) at kernel/qapplication.cpp:4302 #18 0xb5e63bf7 in QApplication::notify (this=0xbfd41380, receiver=0x84725f8, e=0x86e3c98) at kernel/qapplication.cpp:3706 #19 0xb75d39d1 in KApplication::notify (this=0xbfd41380, receiver=0x84725f8, event=0x86e3c98) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302 #20 0xb6906e0e in QCoreApplication::notifyInternal (this=0xbfd41380, receiver=0x84725f8, event=0x86e3c98) at kernel/qcoreapplication.cpp:726 #21 0xb690a9b4 in sendEvent (receiver=0x0, event_type=0, data=0x8051d00) at kernel/qcoreapplication.h:215 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8051d00) at kernel/qcoreapplication.cpp:1367 #23 0xb690ab9c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1260 #24 0xb693283d in sendPostedEvents (s=0x8085d10) at kernel/qcoreapplication.h:220 #25 postEventSourceDispatch (s=0x8085d10) at kernel/qeventdispatcher_glib.cpp:276 #26 0xb4073b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0xb4074350 in ?? () from /usr/lib/libglib-2.0.so.0 #28 0xb407460e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0xb6932d4b in QEventDispatcherGlib::processEvents (this=0x8055d10, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #30 0xb5f0c19a in QGuiEventDispatcherGlib::processEvents (this=0x8055d10, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0xb690611d in QEventLoop::processEvents (this=0xbfd41234, flags=...) at kernel/qeventloop.cpp:149 #32 0xb6906319 in QEventLoop::exec (this=0xbfd41234, flags=...) at kernel/qeventloop.cpp:201 #33 0xb690ac70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #34 0xb5e59164 in QApplication::exec () at kernel/qapplication.cpp:3581 #35 0x0804aa83 in main (argc=1, argv=0x9) at /usr/src/debug/kdepim-4.4.4/kmail/main.cpp:156 Possible duplicates by query: bug 246627, bug 246502, bug 245515, bug 240456. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 240456 ***