Bug 242318

Summary: Kontact crash on start if read an filter imap accounts
Product: [Applications] kontact Reporter: common
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.4.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description common 2010-06-21 08:15:38 UTC
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic x86_64
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
If I start Kontact, ever time the first start Kontact will crash if it's read all emails from two accounts and filter it into sub directories. It's crash - I do nothing, no click or what else. After the crash I restart Kontact and it works well a lot of time.

The crash can be reproduced every time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KMail::ActionScheduler::actionMessage (this=0x1b9c7d0, res=<value optimized out>) at ../../kmail/actionscheduler.cpp:675
#6  0x00007fe90cf15328 in KMail::ActionScheduler::filterMessage (this=0x1b9c7d0) at ../../kmail/actionscheduler.cpp:648
#7  0x00007fe90cf15c54 in KMail::ActionScheduler::qt_metacall (this=0x1b9c7d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc6cb7920) at ./actionscheduler.moc:130
#8  0x00007fe925e92e3f in QMetaObject::activate (sender=0x1b59af0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1cb6068) at kernel/qobject.cpp:3293
#9  0x00007fe925e8fa63 in QObject::event (this=0x1b59af0, e=0x7fffc6cb8070) at kernel/qobject.cpp:1212
#10 0x00007fe92523922c in QApplicationPrivate::notify_helper (this=0xc3bbf0, receiver=0x1b59af0, e=0x7fffc6cb8070) at kernel/qapplication.cpp:4300
#11 0x00007fe92523f6fb in QApplication::notify (this=0x7fffc6cb84a0, receiver=0x1b59af0, e=0x7fffc6cb8070) at kernel/qapplication.cpp:4183
#12 0x00007fe926868526 in KApplication::notify (this=0x7fffc6cb84a0, receiver=0x1b59af0, event=0x7fffc6cb8070) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007fe925e8006c in QCoreApplication::notifyInternal (this=0x7fffc6cb84a0, receiver=0x1b59af0, event=0x7fffc6cb8070) at kernel/qcoreapplication.cpp:704
#14 0x00007fe925eacd42 in QCoreApplication::sendEvent (this=0xc45180) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0xc45180) at kernel/qeventdispatcher_unix.cpp:603
#16 0x00007fe925ea9848 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#18 0x00007fe91d5ef8c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00007fe91d5f3748 in ?? () from /lib/libglib-2.0.so.0
#20 0x00007fe91d5f38fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0x00007fe925ea9513 in QEventDispatcherGlib::processEvents (this=0xc10d70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#22 0x00007fe9252e946e in QGuiEventDispatcherGlib::processEvents (this=0x1b6e2a0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007fe925e7e992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007fe925e7ed6c in QEventLoop::exec (this=0xd32460, flags=) at kernel/qeventloop.cpp:201
#25 0x00007fe926d39411 in Akonadi::Control::Private::exec (this=0xd5e4e0) at ../../akonadi/control.cpp:137
#26 0x00007fe926d39b75 in Akonadi::Control::start (parent=0x0) at ../../akonadi/control.cpp:233
#27 0x0000000000403e72 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:204

This bug may be a duplicate of or related to bug 169048.

Possible duplicates by query: bug 238884, bug 232678, bug 222004, bug 221620, bug 219926.

Reported using DrKonqi
Comment 1 Christophe Marin 2010-06-21 11:15:52 UTC

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