Bug 268677 - No Idea Why it crashes.
Summary: No Idea Why it crashes.
Status: RESOLVED DUPLICATE of bug 169048
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-16 19:28 UTC by Chris
Modified: 2011-03-16 22:45 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-16 19:28: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: Kontact is running and then crashes.  This has happened 10 times in the last 3 hours.  I have noticed that while Kmail is checking for new email it crashes.  However there have also been at least three crashes where I did not see the progress bar in the lower  left showing any activity.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x1630a00, res=<value optimized out>) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:675
#7  0x00007f38299e26a5 in KMail::ActionScheduler::filterMessage (this=0x1630a00) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:648
#8  0x00007f38299e2a54 in KMail::ActionScheduler::qt_metacall (this=0x1630a00, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fff32912860)
    at /usr/src/debug/kdepim-4.4.10/build/kmail/actionscheduler.moc:130
#9  0x00007f384355c88f in QMetaObject::activate (sender=0x16bd850, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x00007f384355b239 in QObject::event (this=0x16bd850, e=<value optimized out>) at kernel/qobject.cpp:1181
#11 0x00007f3842902114 in QApplicationPrivate::notify_helper (this=0x63c110, receiver=0x16bd850, e=0x7fff32913000) at kernel/qapplication.cpp:4462
#12 0x00007f384290a6aa in QApplication::notify (this=<value optimized out>, receiver=0x16bd850, e=0x7fff32913000) at kernel/qapplication.cpp:4341
#13 0x00007f3843e8a876 in KApplication::notify (this=0x7fff329133c0, receiver=0x16bd850, event=0x7fff32913000) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#14 0x00007f384354763c in QCoreApplication::notifyInternal (this=0x7fff329133c0, receiver=0x16bd850, event=0x7fff32913000) at kernel/qcoreapplication.cpp:731
#15 0x00007f3843574ee8 in sendEvent (this=0x63fa70) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x63fa70) at kernel/qeventdispatcher_unix.cpp:619
#17 0x00007f3843571c58 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 0x00007f383ac16a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f383ac17270 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f383ac17510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f384357230f in QEventDispatcherGlib::processEvents (this=0x6132c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007f38429a7b8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f3843546a72 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f3843546c85 in QEventLoop::exec (this=0x7fff32913310, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f384354b0eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#27 0x000000000040417e in _start ()

Possible duplicates by query: bug 268560, bug 268468, bug 268464, bug 268232, bug 268226.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-03-16 22:45:22 UTC
(In reply to comment #0)

> -- Information about the crash:
> - What I was doing when the application crashed: Kontact is running and then
> crashes.  This has happened 10 times in the last 3 hours.  I have noticed that
> while Kmail is checking for new email it crashes.  However there have also been
> at least three crashes where I did not see the progress bar in the lower  left
> showing any activity.
> 

How about reading https://bugs.kde.org/show_bug.cgi?id=169048#c63

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