Bug 268152

Summary: Only after Akonadi is configured
Product: [Applications] kontact Reporter: Chris <crglasoe>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.4.10   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Chris 2011-03-10 20:39:29 UTC
Application: kontact (4.4.10)
KDE Platform Version: 4.5.5 (KDE 4.5.5) "release 1"
Qt Version: 4.7.2
Operating System: Linux 2.6.34.7-0.7-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: An interesting observation here is that I had to format my hard drive and reload everything.  Akonadi was not syncing my Google calendar.  I remembered that I had to go to configure desktop and network sharing to set direct connect to internet.  Prior to that I did not experience any crashes and I was using kmail for over 4 hours.  Since that change this crash has occurred twice shortly after starting kontact and loading new  email.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x1288f10, res=<value optimized out>) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:675
#7  0x00007f4d681ba6a5 in KMail::ActionScheduler::filterMessage (this=0x1288f10) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:648
#8  0x00007f4d681baa54 in KMail::ActionScheduler::qt_metacall (this=0x1288f10, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fff7e4c64f0)
    at /usr/src/debug/kdepim-4.4.10/build/kmail/actionscheduler.moc:130
#9  0x00007f4d81d3188f in QMetaObject::activate (sender=0x9ba0c0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x00007f4d81d30239 in QObject::event (this=0x9ba0c0, e=<value optimized out>) at kernel/qobject.cpp:1181
#11 0x00007f4d810d7114 in QApplicationPrivate::notify_helper (this=0x642d40, receiver=0x9ba0c0, e=0x7fff7e4c6c90) at kernel/qapplication.cpp:4462
#12 0x00007f4d810df6aa in QApplication::notify (this=<value optimized out>, receiver=0x9ba0c0, e=0x7fff7e4c6c90) at kernel/qapplication.cpp:4341
#13 0x00007f4d8265f876 in KApplication::notify (this=0x7fff7e4c7050, receiver=0x9ba0c0, event=0x7fff7e4c6c90) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#14 0x00007f4d81d1c63c in QCoreApplication::notifyInternal (this=0x7fff7e4c7050, receiver=0x9ba0c0, event=0x7fff7e4c6c90) at kernel/qcoreapplication.cpp:731
#15 0x00007f4d81d49ee8 in sendEvent (this=0x640290) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x640290) at kernel/qeventdispatcher_unix.cpp:619
#17 0x00007f4d81d46c58 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007f4d793eba93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f4d793ec270 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f4d793ec510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f4d81d4730f in QEventDispatcherGlib::processEvents (this=0x6132c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007f4d8117cb8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f4d81d1ba72 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f4d81d1bc85 in QEventLoop::exec (this=0x7fff7e4c6fa0, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f4d81d200eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#27 0x000000000040417e in _start ()

Possible duplicates by query: bug 268151, bug 267496, bug 267387, bug 267073, bug 267057.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-03-11 11:43:14 UTC

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