Application: kontact (4.4 rc1) KDE Platform Version: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)) Qt Version: 4.6.0 Operating System: Linux 2.6.31-18-generic i686 Distribution: Ubuntu 9.10 -- Information about the crash: I simply used kontact and it crached. I don’t know why but it did. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x0367b615 in Akregator::Article::title() const () from /usr/lib/kde4/akregatorpart.so #7 0x03687ed5 in Akregator::ArticleModel::Private::Private(QList<Akregator::Article> const&, Akregator::ArticleModel*) () from /usr/lib/kde4/akregatorpart.so #8 0x03688038 in Akregator::ArticleModel::ArticleModel(QList<Akregator::Article> const&, QObject*) () from /usr/lib/kde4/akregatorpart.so #9 0x036a70f6 in ?? () from /usr/lib/kde4/akregatorpart.so #10 0x036a758f in ?? () from /usr/lib/kde4/akregatorpart.so #11 0x0143911a in QMetaObject::metacall (object=0x942f910, cl=171035456, idx=15, argv=0xbfc760a8) at kernel/qmetaobject.cpp:237 #12 0x0144789b in QMetaObject::activate (sender=0x9a35a98, m=0x1166c48, local_signal_index=0, argv=0xbfc760a8) at kernel/qobject.cpp:3294 #13 0x00ff5a73 in KJob::finished (this=0x9a35a98, _t1=0x9a35a98) at ./kjob.moc:173 #14 0x00ff5c1c in KJob::emitResult (this=0x9a35a98) at ../../kdecore/jobs/kjob.cpp:310 #15 0x036812aa in ?? () from /usr/lib/kde4/akregatorpart.so #16 0x036813e1 in ?? () from /usr/lib/kde4/akregatorpart.so #17 0x0143911a in QMetaObject::metacall (object=0x9a35a98, cl=171035456, idx=26, argv=0xbfc7620c) at kernel/qmetaobject.cpp:237 #18 0x0144789b in QMetaObject::activate (sender=0x9e33028, m=0x1547188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3294 #19 0x0144f527 in QSingleShotTimer::timeout (this=0x9e33028) at .moc/release-shared/qtimer.moc:82 #20 0x0144f63c in QSingleShotTimer::timerEvent (this=0x9e33028) at kernel/qtimer.cpp:308 #21 0x01444704 in QObject::event (this=0x9e33028, e=0xa252690) at kernel/qobject.cpp:1224 #22 0x0571c19c in QApplicationPrivate::notify_helper (this=0x86dbc48, receiver=0x9e33028, e=0xbfc766d0) at kernel/qapplication.cpp:4242 #23 0x05722df7 in QApplication::notify (this=0xbfc76a34, receiver=0x9e33028, e=0xbfc766d0) at kernel/qapplication.cpp:3661 #24 0x00b1367a in KApplication::notify (this=0xbfc76a34, receiver=0x9e33028, event=0xbfc766d0) at ../../kdeui/kernel/kapplication.cpp:302 #25 0x01433eab in QCoreApplication::notifyInternal (this=0xbfc76a34, receiver=0x9e33028, event=0xbfc766d0) at kernel/qcoreapplication.cpp:704 #26 0x01463286 in QCoreApplication::sendEvent (this=0x86e4d3c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #27 QTimerInfoList::activateTimers (this=0x86e4d3c) at kernel/qeventdispatcher_unix.cpp:603 #28 0x0145ff17 in timerSourceDispatch (source=0x86e4d78) at kernel/qeventdispatcher_glib.cpp:184 #29 idleTimerSourceDispatch (source=0x86e4d78) at kernel/qeventdispatcher_glib.cpp:231 #30 0x02972e88 in g_main_dispatch (context=0x86e4100) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960 #31 IA__g_main_context_dispatch (context=0x86e4100) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513 #32 0x02976730 in g_main_context_iterate (context=0x86e4100, block=<value optimized out>, dispatch=1, self=0x86db750) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591 #33 0x02976863 in IA__g_main_context_iteration (context=0x86e4100, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654 #34 0x0145fbd5 in QEventDispatcherGlib::processEvents (this=0x86e3da0, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #35 0x057d9b75 in QGuiEventDispatcherGlib::processEvents (this=0x86e3da0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #36 0x014324c9 in QEventLoop::processEvents (this=0xbfc76994, flags=) at kernel/qeventloop.cpp:149 #37 0x0143291a in QEventLoop::exec (this=0xbfc76994, flags=...) at kernel/qeventloop.cpp:201 #38 0x01436b0f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #39 0x0571c237 in QApplication::exec () at kernel/qapplication.cpp:3570 #40 0x0804b4b6 in _start () Reported using DrKonqi
Reported at bug 194591 Regards *** This bug has been marked as a duplicate of bug 194591 ***