Bug 269389

Summary: Crashed several times
Product: [Applications] kontact Reporter: Otter <otters73>
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 Otter 2011-03-25 14:38:35 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:
I started Kontact/Kmail and it crashed when retrieving email to IMAP accounts.  I restarted and it crashed again.  I had looked at 3 emails.  I restarted and finished reviewing emails.  It crashed again.  However this time it had been running for about 30 minutes.  This has been happening for several weeks.  I have not reported the bugs because I thought someone else would be experiencing the same issues and a resolution would be forth coming.  But now this is becoming very annoying.  Is there anything I can do?

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x134ff40, res=<value optimized out>) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:675
#7  0x00007f455d75a6a5 in KMail::ActionScheduler::filterMessage (this=0x134ff40) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:648
#8  0x00007f455d75aa54 in KMail::ActionScheduler::qt_metacall (this=0x134ff40, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fff992b0de0)
    at /usr/src/debug/kdepim-4.4.10/build/kmail/actionscheduler.moc:130
#9  0x00007f457739488f in QMetaObject::activate (sender=0x1395950, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x00007f4577393239 in QObject::event (this=0x1395950, e=<value optimized out>) at kernel/qobject.cpp:1181
#11 0x00007f457673a114 in QApplicationPrivate::notify_helper (this=0x645b80, receiver=0x1395950, e=0x7fff992b1580) at kernel/qapplication.cpp:4462
#12 0x00007f45767426aa in QApplication::notify (this=<value optimized out>, receiver=0x1395950, e=0x7fff992b1580) at kernel/qapplication.cpp:4341
#13 0x00007f4577cc2876 in KApplication::notify (this=0x7fff992b1940, receiver=0x1395950, event=0x7fff992b1580) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#14 0x00007f457737f63c in QCoreApplication::notifyInternal (this=0x7fff992b1940, receiver=0x1395950, event=0x7fff992b1580) at kernel/qcoreapplication.cpp:731
#15 0x00007f45773acee8 in sendEvent (this=0x63ea50) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x63ea50) at kernel/qeventdispatcher_unix.cpp:619
#17 0x00007f45773a9c58 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 0x00007f456ea4ea93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f456ea4f270 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f456ea4f510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f45773aa30f in QEventDispatcherGlib::processEvents (this=0x6132c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007f45767dfb8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f457737ea72 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f457737ec85 in QEventLoop::exec (this=0x7fff992b1890, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f45773830eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#27 0x000000000040417e in _start ()

Possible duplicates by query: bug 269166, bug 269054, bug 268849, bug 268818, bug 268677.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-03-25 15:26:51 UTC

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