Bug 231935 - akregator crashes after showing old article and clicking on "All feeds"
Summary: akregator crashes after showing old article and clicking on "All feeds"
Status: RESOLVED DUPLICATE of bug 194591
Alias: None
Product: akregator
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: 2010-03-23 20:12 UTC by Hrvoje Vulin
Modified: 2010-03-23 21:46 UTC (History)
1 user (show)

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 Hrvoje Vulin 2010-03-23 20:12:52 UTC
Application that crashed: akregator
Version of the application: 1.5.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-trunk-686 i686
Distribution: Debian GNU/Linux 5.0.4 (lenny)

What I was doing when the application crashed:
I was going through feeds with + and it jumpped to the end of the list and showed an old feed as new. After this when I click on All feeds it crashes. I am using ntp if this can help...

 -- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4865700 (LWP 2967))]

Thread 2 (Thread 0xaf483b70 (LWP 6352)):
#0  0xb783d424 in __kernel_vsyscall ()
#1  0xb50933d2 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0xb62df864 in __pthread_cond_timedwait (cond=0x857f8c0, mutex=0x857f8a8, abstime=0xaf4832ac) at forward.c:152
#3  0xb6e6b59c in QWaitConditionPrivate::wait (this=0x882b7b0, mutex=0x882b7ac, time=30000) at thread/qwaitcondition_unix.cpp:85
#4  QWaitCondition::wait (this=0x882b7b0, mutex=0x882b7ac, time=30000) at thread/qwaitcondition_unix.cpp:159
#5  0xb6e60d7e in QThreadPoolThread::run (this=0x8762d70) at concurrent/qthreadpool.cpp:140
#6  0xb6e6a5e2 in QThreadPrivate::start (arg=0x8762d70) at thread/qthread_unix.cpp:188
#7  0xb508f585 in start_thread (arg=0xaf483b70) at pthread_create.c:300
#8  0xb62d229e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb4865700 (LWP 2967)):
[KCrash Handler]
#6  0xb2edb255 in Akregator::Article::title() const () from /usr/lib/kde4/akregatorpart.so
#7  0xb2ee7dc5 in Akregator::ArticleModel::Private::Private(QList<Akregator::Article> const&, Akregator::ArticleModel*) () from /usr/lib/kde4/akregatorpart.so
#8  0xb2ee7f28 in Akregator::ArticleModel::ArticleModel(QList<Akregator::Article> const&, QObject*) () from /usr/lib/kde4/akregatorpart.so
#9  0xb2f08b16 in ?? () from /usr/lib/kde4/akregatorpart.so
#10 0xb2f08f2f in ?? () from /usr/lib/kde4/akregatorpart.so
#11 0xb6f70303 in QMetaObject::activate (sender=0x8c78768, from_signal_index=4, to_signal_index=4, argv=0xbfc417d8) at kernel/qobject.cpp:3112
#12 0xb6f70f42 in QMetaObject::activate (sender=0x8c78768, m=0xb7306a88, local_signal_index=0, argv=0xbfc417d8) at kernel/qobject.cpp:3186
#13 0xb719d6d3 in KJob::finished (this=0x8c78768, _t1=0x8c78768) at ./kjob.moc:167
#14 0xb719d99d in KJob::emitResult (this=0x8c78768) at ../../kdecore/jobs/kjob.cpp:302
#15 0xb2ee23aa in ?? () from /usr/lib/kde4/akregatorpart.so
#16 0xb2ee24f1 in ?? () from /usr/lib/kde4/akregatorpart.so
#17 0xb6f70303 in QMetaObject::activate (sender=0x85715d8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#18 0xb6f70f42 in QMetaObject::activate (sender=0x85715d8, m=0xb704bd88, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#19 0xb6f76007 in QSingleShotTimer::timeout (this=0x85715d8) at .moc/release-shared/qtimer.moc:76
#20 0xb6f7612c in QSingleShotTimer::timerEvent (this=0x85715d8) at kernel/qtimer.cpp:298
#21 0xb6f6b39f in QObject::event (this=0x85715d8, e=0xbfc41dac) at kernel/qobject.cpp:1074
#22 0xb659aa94 in QApplicationPrivate::notify_helper (this=0x846fe28, receiver=0x85715d8, e=0xbfc41dac) at kernel/qapplication.cpp:4065
#23 0xb65a2bee in QApplication::notify (this=0xbfc42088, receiver=0x85715d8, e=0xbfc41dac) at kernel/qapplication.cpp:3605
#24 0xb74e0e2a in KApplication::notify (this=0xbfc42088, receiver=0x85715d8, event=0xbfc41dac) at ../../kdeui/kernel/kapplication.cpp:302
#25 0xb6f5b1eb in QCoreApplication::notifyInternal (this=0xbfc42088, receiver=0x85715d8, event=0xbfc41dac) at kernel/qcoreapplication.cpp:610
#26 0xb6f89e21 in QCoreApplication::sendEvent (this=0x8472984) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#27 QTimerInfoList::activateTimers (this=0x8472984) at kernel/qeventdispatcher_unix.cpp:580
#28 0xb6f86317 in timerSourceDispatch (source=0x84729c0) at kernel/qeventdispatcher_glib.cpp:184
#29 idleTimerSourceDispatch (source=0x84729c0) at kernel/qeventdispatcher_glib.cpp:231
#30 0xb50dab38 in g_main_dispatch (context=0x8471e90) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:1960
#31 IA__g_main_context_dispatch (context=0x8471e90) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2513
#32 0xb50de3d0 in g_main_context_iterate (context=0x8471e90, block=<value optimized out>, dispatch=1, self=0x846f7b0) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2591
#33 0xb50de503 in IA__g_main_context_iteration (context=0x8471e90, may_block=1) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2654
#34 0xb6f86041 in QEventDispatcherGlib::processEvents (this=0x8451000, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#35 0xb663a305 in QGuiEventDispatcherGlib::processEvents (this=0x8451000, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#36 0xb6f5983a in QEventLoop::processEvents (this=0xbfc42020, flags=...) at kernel/qeventloop.cpp:149
#37 0xb6f59c82 in QEventLoop::exec (this=0xbfc42020, flags=...) at kernel/qeventloop.cpp:201
#38 0xb6f5c0d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0xb659a917 in QApplication::exec () at kernel/qapplication.cpp:3525
#40 0x0804f961 in _start ()

This bug may be a duplicate of or related to bug 228107

Reported using DrKonqi
Comment 1 Dario Andres 2010-03-23 21:46:08 UTC
THis issue is being tracked at bug 194591. Regards

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