Bug 276800 - KMail crashes in background
Summary: KMail crashes in background
Status: RESOLVED DUPLICATE of bug 277069
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 2.0.95
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-30 07:11 UTC by Frédéric COIFFIER
Modified: 2011-08-02 20:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric COIFFIER 2011-06-30 07:11:49 UTC
Application: kmail (2.0.95)
KDE Platform Version: 4.6.90 (4.7 RC1)
Qt Version: 4.7.3
Operating System: Linux 2.6.38-gentoo-r5 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
KMail was running for several minutes and was in background when it crashed.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  detach (this=0x690061006d005f, kiddo=0x41282b0) at /usr/include/qt4/QtCore/qmap.h:202
#7  remove (this=0x690061006d005f, kiddo=0x41282b0) at /usr/include/qt4/QtCore/qmap.h:660
#8  KPIM::ProgressItem::removeChild (this=0x690061006d005f, kiddo=0x41282b0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90/libkdepim/progressmanager.cpp:73
#9  0x00007f0653524bc1 in KPIM::ProgressItem::setComplete (this=0x41282b0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90/libkdepim/progressmanager.cpp:58
#10 0x00007f065352664d in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x44558a0, instance=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90/libkdepim/agentprogressmonitor.cpp:86
#11 0x00007f06535267e2 in KPIM::AgentProgressMonitor::qt_metacall (this=0x44fec30, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5bf08e10) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6.90/work/kdepim-common-libs-4.6.90_build/libkdepim/agentprogressmonitor.moc:78
#12 0x00007f0659dea96f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007f0655addb65 in Akonadi::AgentManager::instanceStatusChanged (this=0x690061006d005f, _t1=<value optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.6.90/work/kdepimlibs-4.6.90_build/akonadi/agentmanager.moc:177
#14 0x00007f0655ae379b in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged (this=0x1722530, 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
#15 0x00007f0655ae3fa6 in Akonadi::AgentManager::qt_metacall (this=0x1721d10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5bf08fc0) at /var/tmp/portage/kde-base/kdepimlibs-4.6.90/work/kdepimlibs-4.6.90_build/akonadi/agentmanager.moc:131
#16 0x00007f0659dea96f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007f0655bf32ab in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged (this=0x690061006d005f, _t1=<value optimized out>, _t2=0, _t3=<value optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.6.90/work/kdepimlibs-4.6.90_build/akonadi/agentmanagerinterface.moc:285
#18 0x00007f0655bf387f in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall (this=0x1666f90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5bf09700) at /var/tmp/portage/kde-base/kdepimlibs-4.6.90/work/kdepimlibs-4.6.90_build/akonadi/agentmanagerinterface.moc:167
#19 0x00007f065753b739 in ?? () from /usr/lib64/qt4/libQtDBus.so.4
#20 0x00007f065754546f in ?? () from /usr/lib64/qt4/libQtDBus.so.4
#21 0x00007f0659de4a1e in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007f065a2cc8cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#23 0x00007f065a2d1d6d in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#24 0x00007f065bbde896 in KApplication::notify (this=0x7fff5bf0a430, receiver=0x1666f90, event=0x42116d0) at /var/tmp/portage/kde-base/kdelibs-4.6.90/work/kdelibs-4.6.90/kdeui/kernel/kapplication.cpp:311
#25 0x00007f0659dd2c8b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#26 0x00007f0659dd5c11 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4
#27 0x00007f0659dff233 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#28 0x00007f0651c20b91 in g_main_dispatch (context=0x14894e0) at gmain.c:2441
#29 g_main_context_dispatch (context=0x14894e0) at gmain.c:3014
#30 0x00007f0651c25228 in g_main_context_iterate (context=0x14894e0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:3092
#31 0x00007f0651c253dc in g_main_context_iteration (context=0x14894e0, may_block=1) at gmain.c:3155
#32 0x00007f0659dfed73 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#33 0x00007f065a37ecbe in ?? () from /usr/lib64/qt4/libQtGui.so.4
#34 0x00007f0659dd19e2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#35 0x00007f0659dd1dc4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#36 0x00007f0659dd5e3b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#37 0x000000000040328c in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kmail-4.6.90-r1/work/kmail-4.6.90/kmail/main.cpp:145

Possible duplicates by query: bug 276404, bug 276186, bug 268807, bug 267141, bug 265076.

Reported using DrKonqi
Comment 1 Laurent Montel 2011-07-05 11:15:38 UTC
Please update your kmail
I fixed it for 4.6/4.7/trunk
Regards
Comment 2 Christophe Marin 2011-08-02 20:29:36 UTC

*** This bug has been marked as a duplicate of bug 277069 ***