Bug 208123 - Kontact running when crash occurs
Summary: Kontact running when crash occurs
Status: RESOLVED DUPLICATE of bug 200137
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-21 22:35 UTC by Ed
Modified: 2009-09-22 03:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed 2009-09-21 22:35:48 UTC
Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic x86_64
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KMail::FolderJob::msgList (this=0x3fca130) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#6  0x00007f535fdf6d65 in KMAcctImap::ignoreJobsForMessage (this=0x1ae71c0, msg=0x2f27700) at /build/buildd/kdepim-4.3.1/kmail/kmacctimap.cpp:215
#7  0x00007f535ff143cf in KMCommand::transferSelectedMsgs (this=0x3ea2f50) at /build/buildd/kdepim-4.3.1/kmail/kmcommands.cpp:334
#8  0x00007f535ff148d6 in KMCommand::slotStart (this=0x3ea2f50) at /build/buildd/kdepim-4.3.1/kmail/kmcommands.cpp:266
#9  0x00007f535ff058c2 in KMCommand::qt_metacall (this=0x3ea2f50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff78392c60)
    at /build/buildd/kdepim-4.3.1/obj-x86_64-linux-gnu/kmail/kmcommands.moc:86
#10 0x00007f536aadeea2 in QMetaObject::activate (sender=0x47e4290, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x49e8fe0) at kernel/qobject.cpp:3113
#11 0x00007f536aae414f in QSingleShotTimer::timerEvent (this=0x47e4290) at kernel/qtimer.cpp:298
#12 0x00007f536aad9263 in QObject::event (this=0x47e4290, e=0x3fca130) at kernel/qobject.cpp:1075
#13 0x00007f536b64af4d in QApplicationPrivate::notify_helper (this=0x12c8070, receiver=0x47e4290, e=0x7fff78393320) at kernel/qapplication.cpp:4056
#14 0x00007f536b65318a in QApplication::notify (this=0x7fff78393670, receiver=0x47e4290, e=0x7fff78393320) at kernel/qapplication.cpp:4021
#15 0x00007f536ca50deb in KApplication::notify (this=0x7fff78393670, receiver=0x47e4290, event=0x7fff78393320) at /build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302
#16 0x00007f536aac96ac in QCoreApplication::notifyInternal (this=0x7fff78393670, receiver=0x47e4290, event=0x7fff78393320) at kernel/qcoreapplication.cpp:610
#17 0x00007f536aaf6516 in QTimerInfoList::activateTimers (this=0x12c5390) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0x00007f536aaf2b2d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#19 0x0000003002e3a20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0x0000003002e3d8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x0000003002e3da7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0x00007f536aaf2a8f in QEventDispatcherGlib::processEvents (this=0x129a0a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#23 0x00007f536b6e3bdf in QGuiEventDispatcherGlib::processEvents (this=0x7fff78392a00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#24 0x00007f536aac7f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 2017015184}) at kernel/qeventloop.cpp:149
#25 0x00007f536aac8314 in QEventLoop::exec (this=0x7fff783935d0, flags={i = 2017015264}) at kernel/qeventloop.cpp:201
#26 0x00007f536aaca5e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x0000000000404945 in main (argc=1, argv=0x7fff78393d58) at /build/buildd/kdepim-4.3.1/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Thomas McGuire 2009-09-22 03:05:27 UTC

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