Bug 269166 - Crash @ startup
Summary: Crash @ startup
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.10
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-22 19:06 UTC by Chris
Modified: 2011-03-22 21:06 UTC (History)
0 users

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 Chris 2011-03-22 19:06:43 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: started Kontact after re-boot.  Kontact opened to Kmail screen then crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x17f31b0, res=<value optimized out>) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:675
#7  0x00007f43451506a5 in KMail::ActionScheduler::filterMessage (this=0x17f31b0) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:648
#8  0x00007f4345150a54 in KMail::ActionScheduler::qt_metacall (this=0x17f31b0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffc62483c0)
    at /usr/src/debug/kdepim-4.4.10/build/kmail/actionscheduler.moc:130
#9  0x00007f435ed8688f in QMetaObject::activate (sender=0x23e6e00, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x00007f435ed85239 in QObject::event (this=0x23e6e00, e=<value optimized out>) at kernel/qobject.cpp:1181
#11 0x00007f435e12c114 in QApplicationPrivate::notify_helper (this=0x645b30, receiver=0x23e6e00, e=0x7fffc6248b60) at kernel/qapplication.cpp:4462
#12 0x00007f435e1346aa in QApplication::notify (this=<value optimized out>, receiver=0x23e6e00, e=0x7fffc6248b60) at kernel/qapplication.cpp:4341
#13 0x00007f435f6b4876 in KApplication::notify (this=0x7fffc6248f20, receiver=0x23e6e00, event=0x7fffc6248b60) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#14 0x00007f435ed7163c in QCoreApplication::notifyInternal (this=0x7fffc6248f20, receiver=0x23e6e00, event=0x7fffc6248b60) at kernel/qcoreapplication.cpp:731
#15 0x00007f435ed9eee8 in sendEvent (this=0x63eb10) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x63eb10) at kernel/qeventdispatcher_unix.cpp:619
#17 0x00007f435ed9bc58 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 0x00007f4356440a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f4356441270 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f4356441510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f435ed9c30f in QEventDispatcherGlib::processEvents (this=0x6132c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007f435e1d1b8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f435ed70a72 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f435ed70c85 in QEventLoop::exec (this=0x7fffc6248e70, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f435ed750eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#27 0x000000000040417e in _start ()

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

Reported using DrKonqi
Comment 1 Christophe Marin 2011-03-22 21:06:26 UTC
you already reported the same crash countless time. Read the answers that were made to your previous reports.