Application: kmail (2.0.89) KDE Platform Version: 4.6.00 (4.6.0) Qt Version: 4.7.0 Operating System: Linux 2.6.35-25-generic i686 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: since this morning, inbox folder is empty !! I have got 2 unread messages but I see them and other message too. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb64af950 (LWP 15957))] Thread 3 (Thread 0xb3f64b70 (LWP 15963)): #0 0x0054e416 in __kernel_vsyscall () #1 0x0173f4dc in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0x01bbfd9d in __pthread_cond_wait (cond=0xb76d3770, mutex=0xb76d3758) at forward.c:139 #3 0xb71cb3a5 in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xb71cb481 in ?? () from /usr/lib/libQtWebKit.so.4 #5 0x0173acc9 in start_thread (arg=0xb3f64b70) at pthread_create.c:304 #6 0x01bb269e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb213fb70 (LWP 15968)): #0 0x037b8e36 in clock_gettime (clock_id=58445812, tp=0xb213ef70) at ../sysdeps/unix/clock_gettime.c:100 #1 0x06b0150b in do_gettime () at tools/qelapsedtimer_unix.cpp:105 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:119 #3 0x06bd86e5 in QTimerInfoList::updateCurrentTime (this=0xb1801934) at kernel/qeventdispatcher_unix.cpp:339 #4 0x06bd872a in QTimerInfoList::timerWait (this=0xb1801934, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x06bd67a8 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb213f09c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x06bd683d in timerSourcePrepare (source=0x0, timeout=0x37bcff4) at kernel/qeventdispatcher_glib.cpp:169 #7 0x02466e6a in g_main_context_prepare () from /lib/libglib-2.0.so.0 #8 0x02467279 in ?? () from /lib/libglib-2.0.so.0 #9 0x02467848 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #10 0x06bd659f in QEventDispatcherGlib::processEvents (this=0x8d45e00, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #11 0x06ba6609 in QEventLoop::processEvents (this=0xb213f270, flags=) at kernel/qeventloop.cpp:149 #12 0x06ba6a8a in QEventLoop::exec (this=0xb213f270, flags=...) at kernel/qeventloop.cpp:201 #13 0x06aa2b7e in QThread::exec (this=0x8d44038) at thread/qthread.cpp:490 #14 0x06b8535b in QInotifyFileSystemWatcherEngine::run (this=0x8d44038) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x06aa5df9 in QThreadPrivate::start (arg=0x8d44038) at thread/qthread_unix.cpp:266 #16 0x0173acc9 in start_thread (arg=0xb213fb70) at pthread_create.c:304 #17 0x01bb269e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb64af950 (LWP 15957)): [KCrash Handler] #7 detach (this=0x382c7574, kiddo=0x8d521b8) at /usr/include/qt4/QtCore/qmap.h:202 #8 remove (this=0x382c7574, kiddo=0x8d521b8) at /usr/include/qt4/QtCore/qmap.h:659 #9 KPIM::ProgressItem::removeChild (this=0x382c7574, kiddo=0x8d521b8) at ../../libkdepim/progressmanager.cpp:73 #10 0x01db13d9 in KPIM::ProgressItem::setComplete (this=0x8d521b8) at ../../libkdepim/progressmanager.cpp:58 #11 0x01db3124 in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x8d70068, instance=...) at ../../libkdepim/agentprogressmonitor.cpp:86 #12 0x01db32a0 in KPIM::AgentProgressMonitor::qt_metacall (this=0x8a4d408, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf925898) at ./agentprogressmonitor.moc:78 #13 0x06bad8ca in QMetaObject::metacall (object=0x8a4d408, cl=114145720, idx=6, argv=0xbf925898) at kernel/qmetaobject.cpp:237 #14 0x06bc06ad in QMetaObject::activate (sender=0x87d61a8, m=0x53e456c, local_signal_index=4, argv=0x382c7574) at kernel/qobject.cpp:3280 #15 0x0523f4e3 in Akonadi::AgentManager::instanceStatusChanged (this=0x87d61a8, _t1=...) at ./agentmanager.moc:177 #16 0x0523f97f in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged (this=0x86fc220, identifier=..., status=2, msg=...) at ../../akonadi/agentmanager.cpp:129 #17 0x05246473 in Akonadi::AgentManager::qt_metacall (this=0x87d61a8, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0xbf9259f0) at ./agentmanager.moc:131 #18 0x06bad8ca in QMetaObject::metacall (object=0x87d61a8, cl=114145720, idx=18, argv=0xbf9259f0) at kernel/qmetaobject.cpp:237 #19 0x06bc06ad in QMetaObject::activate (sender=0x86fc100, m=0x53e9724, local_signal_index=7, argv=0x382c7574) at kernel/qobject.cpp:3280 #20 0x053735af in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged (this=0x86fc100, _t1=..., _t2=2, _t3=...) at agentmanagerinterface.moc:285 #21 0x05373e64 in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall (this=0x86fc100, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbf925dcc) at agentmanagerinterface.moc:167 #22 0x07c109dc in QDBusConnectionPrivate::deliverCall (this=0x864a840, object=0x86fc100, msg=..., metaTypes=..., slotIdx=12) at qdbusintegrator.cpp:919 #23 0x07c1c1f7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8b8d0b0, object=0x86fc100) at qdbusintegrator_p.h:103 #24 0x06bba6a2 in QObject::event (this=0x86fc100, e=0x86f5e38) at kernel/qobject.cpp:1219 #25 0x00d97fdc in QApplicationPrivate::notify_helper (this=0x8657af8, receiver=0x86fc100, e=0x8b8d0b0) at kernel/qapplication.cpp:4396 #26 0x00d9e04e in QApplication::notify (this=0xbf9266dc, receiver=0x86fc100, e=0x8b8d0b0) at kernel/qapplication.cpp:3798 #27 0x00319f7a in KApplication::notify (this=0xbf9266dc, receiver=0x86fc100, event=0x8b8d0b0) at ../../kdeui/kernel/kapplication.cpp:311 #28 0x06ba7b3b in QCoreApplication::notifyInternal (this=0xbf9266dc, receiver=0x86fc100, event=0x8b8d0b0) at kernel/qcoreapplication.cpp:732 #29 0x06baad8b in sendEvent (receiver=0x0, event_type=0, data=0x8623d28) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8623d28) at kernel/qcoreapplication.cpp:1373 #31 0x06baaf4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266 #32 0x06bd6a74 in sendPostedEvents (s=0x8659d10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #33 postEventSourceDispatch (s=0x8659d10) at kernel/qeventdispatcher_glib.cpp:277 #34 0x02463855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #35 0x02467668 in ?? () from /lib/libglib-2.0.so.0 #36 0x02467848 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #37 0x06bd6565 in QEventDispatcherGlib::processEvents (this=0x86237f8, flags=...) at kernel/qeventdispatcher_glib.cpp:415 #38 0x00e59be5 in QGuiEventDispatcherGlib::processEvents (this=0x86237f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #39 0x06ba6609 in QEventLoop::processEvents (this=0xbf9265f4, flags=) at kernel/qeventloop.cpp:149 #40 0x06ba6a8a in QEventLoop::exec (this=0xbf9265f4, flags=...) at kernel/qeventloop.cpp:201 #41 0x06bab00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #42 0x00d96e07 in QApplication::exec () at kernel/qapplication.cpp:3672 #43 0x0804a4e6 in main (argc=3, argv=0xbf926894) at ../../kmail/main.cpp:145 Possible duplicates by query: bug 264662, bug 261487. Reported using DrKonqi
Created attachment 57958 [details] New crash information added by DrKonqi kmail (2.0.89) on KDE Platform 4.6.1 (4.6.1) using Qt 4.7.2 - What I was doing when the application crashed: i had this bug when i opened kmail after login -- Backtrace (Reduced): #6 detach (this=0x69, akey=@0x7fff687caaa8) at /usr/include/qt4/QtCore/qmap.h:202 #7 QMap<KPIM::ProgressItem*, bool>::remove (this=0x69, akey=@0x7fff687caaa8) at /usr/include/qt4/QtCore/qmap.h:660 #8 0x00007f213ee6447b in KPIM::ProgressItem::removeChild (this=0x31, kiddo=0x17d1220) at ../../libkdepim/progressmanager.cpp:73 #9 0x00007f213ee644e1 in KPIM::ProgressItem::setComplete (this=0x17d1220) at ../../libkdepim/progressmanager.cpp:58 #10 0x00007f213ee6590d in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x1b40ce0, instance=...) at ../../libkdepim/agentprogressmonitor.cpp:86
*** Bug 265242 has been marked as a duplicate of this bug. ***
*** Bug 268807 has been marked as a duplicate of this bug. ***
*** Bug 267141 has been marked as a duplicate of this bug. ***
Can anyone get a valgrind report? valgrind kmail --nofork &> report
Hi ! I can't sorry because I come back to kmail 1.13.5.
Created attachment 61057 [details] New crash information added by DrKonqi kmail (2.1.0) on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.3 - What I was doing when the application crashed: I got a Conflict resolution box : When I clicked on "Right" choice, I got this crash. -- Backtrace (Reduced): #6 detach (this=0xffffffff, kiddo=0x9fe6620) at /usr/include/qt4/QtCore/qmap.h:202 #7 remove (this=0xffffffff, kiddo=0x9fe6620) at /usr/include/qt4/QtCore/qmap.h:660 #8 KPIM::ProgressItem::removeChild (this=0xffffffff, kiddo=0x9fe6620) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.0/work/kdepim-common-libs-4.6.0/libkdepim/progressmanager.cpp:73 #9 0x00007f623b31abe1 in KPIM::ProgressItem::setComplete (this=0x9fe6620) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.0/work/kdepim-common-libs-4.6.0/libkdepim/progressmanager.cpp:58 #10 0x00007f623b31c66d in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x71e4960, instance=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.0/work/kdepim-common-libs-4.6.0/libkdepim/agentprogressmonitor.cpp:86
I had same problem after a bigger update of my packages. After some inspection of packages, I noticed that not all was upgraded due to my wrong settings of the package manager (portage, gentoo). So some dependencies of kmail wasn't updated. I think the kde-misc/kwebkitpart was the main problem, but not sure. That had version 0.9.6 while 1.1.1 was out, and I seen some webkit related files in the crash report. Hope will help for some ppl.
*** Bug 277773 has been marked as a duplicate of this bug. ***
Created attachment 61898 [details] valgrind log for kontact For whatever reason 'valgrind kmail' hangs after memory checking but with 'valgrind kontact --nofork' I got this report.
fixed in master/4.7
*** Bug 276186 has been marked as a duplicate of this bug. ***
*** Bug 264662 has been marked as a duplicate of this bug. ***
*** Bug 277369 has been marked as a duplicate of this bug. ***
*** Bug 278174 has been marked as a duplicate of this bug. ***