Bug 264114

Summary: akregator kontact unexpected crash
Product: [Applications] kontact Reporter: przxqgl <salamandir>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description przxqgl 2011-01-23 21:16:44 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-22-generic i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x02d17225 in Akregator::Article::title() const () from /usr/lib/kde4/akregatorpart.so
#7  0x02d23d75 in Akregator::ArticleModel::Private::Private(QList<Akregator::Article> const&, Akregator::ArticleModel*) () from /usr/lib/kde4/akregatorpart.so
#8  0x02d23ed8 in Akregator::ArticleModel::ArticleModel(QList<Akregator::Article> const&, QObject*) () from /usr/lib/kde4/akregatorpart.so
#9  0x02d44b66 in ?? () from /usr/lib/kde4/akregatorpart.so
#10 0x02d44f7f in ?? () from /usr/lib/kde4/akregatorpart.so
#11 0x00ba1263 in QMetaObject::activate (sender=0xaaaa358, from_signal_index=4, to_signal_index=4, argv=0xbfbcc4b8) at kernel/qobject.cpp:3113
#12 0x00ba1ec2 in QMetaObject::activate (sender=0xaaaa358, m=0xa43d68, local_signal_index=0, argv=0xbfbcc4b8) at kernel/qobject.cpp:3187
#13 0x008de193 in KJob::finished (this=0xaaaa358, _t1=0xaaaa358) at ./kjob.moc:167
#14 0x008de45d in KJob::emitResult (this=0xaaaa358) at ../../kdecore/jobs/kjob.cpp:302
#15 0x02d1e35a in ?? () from /usr/lib/kde4/akregatorpart.so
#16 0x02d1e4a1 in ?? () from /usr/lib/kde4/akregatorpart.so
#17 0x00ba1263 in QMetaObject::activate (sender=0xa0af7a0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#18 0x00ba1ec2 in QMetaObject::activate (sender=0xa0af7a0, m=0xc7b908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#19 0x00ba6387 in QSingleShotTimer::timeout (this=0xa0af7a0) at .moc/release-shared/qtimer.moc:76
#20 0x00ba649c in QSingleShotTimer::timerEvent (this=0xa0af7a0) at kernel/qtimer.cpp:298
#21 0x00b9b3bf in QObject::event (this=0xa0af7a0, e=0xbfbcca80) at kernel/qobject.cpp:1075
#22 0x010eaf54 in QApplicationPrivate::notify_helper (this=0x9890f38, receiver=0xa0af7a0, e=0xbfbcca80) at kernel/qapplication.cpp:4056
#23 0x010f267c in QApplication::notify (this=0xbfbccde4, receiver=0xa0af7a0, e=0xbfbcca80) at kernel/qapplication.cpp:3603
#24 0x00607bfa in KApplication::notify (this=0xbfbccde4, receiver=0xa0af7a0, event=0xbfbcca80) at ../../kdeui/kernel/kapplication.cpp:302
#25 0x00b8b6cb in QCoreApplication::notifyInternal (this=0xbfbccde4, receiver=0xa0af7a0, event=0xbfbcca80) at kernel/qcoreapplication.cpp:610
#26 0x00bb87ce in QCoreApplication::sendEvent (this=0x987df3c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#27 QTimerInfoList::activateTimers (this=0x987df3c) at kernel/qeventdispatcher_unix.cpp:572
#28 0x00bb60e0 in timerSourceDispatch (source=0x987df08) at kernel/qeventdispatcher_glib.cpp:165
#29 0x02e8ae88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x02e8e730 in ?? () from /lib/libglib-2.0.so.0
#31 0x02e8e863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x00bb602c in QEventDispatcherGlib::processEvents (this=0x985d9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#33 0x0118bbe5 in QGuiEventDispatcherGlib::processEvents (this=0x985d9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00b89c79 in QEventLoop::processEvents (this=0xbfbccd44, flags=) at kernel/qeventloop.cpp:149
#35 0x00b8a0ca in QEventLoop::exec (this=0xbfbccd44, flags=...) at kernel/qeventloop.cpp:201
#36 0x00b8c53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x010eadd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804b4e6 in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2011-01-24 00:00:05 UTC

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