Summary: | KMail2 deadlocks on mail check when coflict dialog is shown | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | András Manţia <amantia> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | a, frederic.coiffier, ht990332, jjm, woebbeking |
Priority: | NOR | ||
Version: | Git (master) | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
András Manţia
2011-06-16 08:43:26 UTC
I have the same behaviour very often (with KDE 4.7rc1/KMail 2.0.95) : the conflict resolution box appears but I can't click on a button. Gdb gives exactly the same backtrace : #0 0x00007f3529991f33 in poll () from /lib64/libc.so.6 #1 0x00007f3522133f89 in g_main_context_poll (context=0x7f74e0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:3405 #2 g_main_context_iterate (context=0x7f74e0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:3087 #3 0x00007f35221343dc in g_main_context_iteration (context=0x7f74e0, may_block=1) at gmain.c:3155 #4 0x00007f352a30dd73 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x00007f352a88dcbe in ?? () from /usr/lib64/qt4/libQtGui.so.4 #6 0x00007f352a2e09e2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007f352a2e0dc4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007f352bab53f6 in KJob::exec (this=0x2103210) at /var/tmp/portage/kde-base/kdelibs-4.6.90/work/kdelibs-4.6.90/kdecore/jobs/kjob.cpp:204 #9 0x00007f352b418553 in KMMainWidget::slotEndCheckMail (this=<value optimized out>) at /var/tmp/portage/kde-base/kmail-4.6.90-r1/work/kmail-4.6.90/kmail/kmmainwidget.cpp:390 #10 0x00007f352b41b62d in KMMainWidget::qt_metacall (this=0xc2c7b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc8d9a1a0) at /var/tmp/portage/kde-base/kmail-4.6.90-r1/work/kmail-4.6.90_build/kmail/kmmainwidget.moc:369 #11 0x00007f352a2f996f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #12 0x00007f352b3c4a3c in KMKernel::slotProgressItemCompletedOrCanceled (this=0x7fffc8d9c6c0, item=<value optimized out>) at /var/tmp/portage/kde-base/kmail-4.6.90-r1/work/kmail-4.6.90/kmail/kmkernel.cpp:1660 #13 0x00007f352b3d356c in KMKernel::qt_metacall (this=0x7fffc8d9c6c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc8d9a430) at /var/tmp/portage/kde-base/kmail-4.6.90-r1/work/kmail-4.6.90_build/kmail/kmkernel.moc:205 #14 0x00007f352a2f996f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #15 0x00007f3523a33232 in KPIM::ProgressManager::progressItemCompleted (this=0x34a5860, _t1=0x10f9bf0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90_build/libkdepim/progressmanager.moc:272 #16 0x00007f3523a34aab in KPIM::ProgressManager::qt_metacall (this=0xadb6b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc8d9a570) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90_build/libkdepim/progressmanager.moc:246 #17 0x00007f352a2f996f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #18 0x00007f3523a33482 in KPIM::ProgressItem::progressItemCompleted (this=0x34a5860, _t1=0x10f9bf0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90_build/libkdepim/progressmanager.moc:121 #19 0x00007f3523a33bb0 in KPIM::ProgressItem::setComplete (this=0x10f9bf0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90/libkdepim/progressmanager.cpp:56 #20 0x00007f3523a3564d in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x3143ed0, instance=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90/libkdepim/agentprogressmonitor.cpp:86 #21 0x00007f3523a357e2 in KPIM::AgentProgressMonitor::qt_metacall (this=0x31c5c10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc8d9a6e0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90_build/libkdepim/agentprogressmonitor.moc:78 #22 0x00007f352a2f996f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #23 0x00007f3525fecb65 in Akonadi::AgentManager::instanceStatusChanged (this=0x34a5860, _t1=<value optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.6.90/work/kdepimlibs-4.6.90_build/akonadi/agentmanager.moc:177 #24 0x00007f3525ff279b in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged (this=0x6bded0, identifier=<value optimized out>, status=0, msg=...) at /var/tmp/portage/kde-base/kdepimlibs-4.6.90/work/kdepimlibs-4.6.90/akonadi/agentmanager.cpp:129 #25 0x00007f3525ff2fa6 in Akonadi::AgentManager::qt_metacall (this=0x6bdea0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc8d9a890) at /var/tmp/portage/kde-base/kdepimlibs-4.6.90/work/kdepimlibs-4.6.90_build/akonadi/agentmanager.moc:131 #26 0x00007f352a2f996f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #27 0x00007f35261022ab in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged (this=0x34a5860, _t1=<value optimized out>, _t2=0, _t3=<value optimized out>) In fact, with 4.7rc1, the problem occurs each time the conflict box appears. Git commit e3e527084fc730829919c7a827dfe144029c89b9 by Andras Mantia. Committed on 17/09/2011 at 23:30. Pushed by amantia into branch 'master'. Change synchornous akonadi job execution to async to prevent strange deadlocks. Remove code that doesn't make sense anymore, and try to actually make it work (fails though, too tired to debug it, but see the existing FIXME). BUG: 275789 M +35 -31 kmail/kmmainwidget.cpp M +1 -2 kmail/kmmainwidget.h http://commits.kde.org/kdepim/e3e527084fc730829919c7a827dfe144029c89b9 Will this fix make 4.7 branch as well? *** Bug 281085 has been marked as a duplicate of this bug. *** (In reply to comment #4) > Will this fix make 4.7 branch as well? Unfortunately, it still doesn't present in 4.7 branch. I have tried to compare the patch https://projects.kde.org/projects/kde/kdepim/repository/revisions/e3e527084fc730829919c7a827dfe144029c89b9/diff with C header (kmmainwidget.h) code: https://projects.kde.org/projects/kde/kdepim/repository/entry/kmail/kmmainwidget.h?rev=KDE%2F4.7 @kde-pim team Please, please, include the fix into 4.7.2! KDE's bugzilla doesn't transmit votes from duplicates (I mean Bug 281085) and breaks reality this way :) To my knowledge the fix has not been backported yet to 4.7 branch, but I'll try to do it asap. Git commit 7585e58daed226455d235d2a0a2e61de0a805d4d by Andras Mantia. Committed on 17/09/2011 at 23:30. Pushed by amantia into branch 'KDE/4.7'. Change synchornous akonadi job execution to async to prevent strange deadlocks. Remove code that doesn't make sense anymore, and try to actually make it work (fails though, too tired to debug it, but see the existing FIXME). BUG: 275789 M +35 -26 kmail/kmmainwidget.cpp M +1 -2 kmail/kmmainwidget.h http://commits.kde.org/kdepim/7585e58daed226455d235d2a0a2e61de0a805d4d Andras, really hearty thanks! Have not observed a lockup with the CR dialogue since the commit in comment #3 and the implementation of the separate Email Filter Agent in Akonadi. Still getting the CR occasionally, but I can live with that. Many thanks for the fix! |