Bug 280305 - Akregator crashed trying to read an article
Summary: Akregator crashed trying to read an article
Status: RESOLVED DUPLICATE of bug 163573
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.6
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-18 02:30 UTC by Joshua J. Kugler
Modified: 2011-08-28 21:09 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 Joshua J. Kugler 2011-08-18 02:30:45 UTC
Application: akregator (1.6.6)
KDE Platform Version: 4.7.00 (4.7.0)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-10-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
Akgregator had started, and had successfully retrieved all the feeds.  I had adjusted column widths in the feed list, and then clicked on a feed, sorted by date, scrolled to the top, and clicked on an article. Akregator crashed.

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

Thread 2 (Thread 0xb4a9bb70 (LWP 30830)):
#0  0x00b95416 in __kernel_vsyscall ()
#1  0x03a26f76 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x019d384b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x019c31af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x019c3524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x0099c577 in QEventDispatcherGlib::processEvents (this=0x8f95430, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x0096e289 in QEventLoop::processEvents (this=0xb4a9b270, flags=...) at kernel/qeventloop.cpp:149
#7  0x0096e522 in QEventLoop::exec (this=0xb4a9b270, flags=...) at kernel/qeventloop.cpp:201
#8  0x008782a0 in QThread::exec (this=0x927e818) at thread/qthread.cpp:492
#9  0x0094ffdb in QInotifyFileSystemWatcherEngine::run (this=0x927e818) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x0087ada2 in QThreadPrivate::start (arg=0x927e818) at thread/qthread_unix.cpp:320
#11 0x00cb3e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x03a3573e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb78aa730 (LWP 30827)):
[KCrash Handler]
#7  0x083574d5 in c4_Property::c4_Property (this=0xbfee709c, type_=73 'I', name_=0x0) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1106
#8  0x0834b56a in c4_IntProp (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524
#9  f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228
#10 0x0834bc04 in c4_HandlerSeq::CreateHandler (this=0xaee31d8, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:131
#11 0x08358624 in c4_Sequence::PropIndex (this=0xaee31d8, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:292
#12 0x08358707 in c4_Sequence::Set (this=0xaee31d8, index_=244, prop_=..., buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:325
#13 0x08355d3a in SetData (this=0xaed6f0c, row_=244, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:426
#14 c4_View::SetItem (this=0xaed6f0c, row_=244, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:231
#15 0x08351472 in c4_HashViewer::SetItem (this=0xaed6f08, row_=244, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:366
#16 0x0834347d in DoSet (this=0xaee6768, index_=244, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:154
#17 c4_CustomHandler::Set (this=0xaee6768, index_=244, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:69
#18 0x08358c74 in c4_Sequence::SetAt (this=0xaeee690, index_=244, newElem_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:104
#19 0x0835d277 in SetAt (this=0xaeba9e8, guid=..., status=8) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:89
#20 Akregator::Backend::FeedStorageMK4Impl::setStatus (this=0xaeba9e8, guid=..., status=8) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:396
#21 0x022e7eb1 in Akregator::Article::setStatus (this=0xbfee746c, stat=1) at ../../../akregator/src/article.cpp:367
#22 0x022eb711 in Akregator::ArticleModifyJob::doStart (this=0xc644530) at ../../../akregator/src/articlejobs.cpp:145
#23 0x022ebc51 in Akregator::ArticleModifyJob::qt_metacall (this=0xc644530, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfee756c) at ./articlejobs.moc:180
#24 0x009756ba in QMetaObject::metacall (object=0xc644530, cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0xbfee756c) at kernel/qmetaobject.cpp:237
#25 0x009854ff in QMetaObject::activate (sender=0x9f6e180, m=0xaa9188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3287
#26 0x0098b4d7 in QSingleShotTimer::timeout (this=0x9f6e180) at .moc/release-shared/qtimer.moc:82
#27 0x0098b58c in QSingleShotTimer::timerEvent (this=0x9f6e180) at kernel/qtimer.cpp:308
#28 0x00984214 in QObject::event (this=0x9f6e180, e=0xbfee7a8c) at kernel/qobject.cpp:1190
#29 0x06906d24 in QApplicationPrivate::notify_helper (this=0x8e8a9d0, receiver=0x9f6e180, e=0xbfee7a8c) at kernel/qapplication.cpp:4462
#30 0x0690b8ce in QApplication::notify (this=0xbfee7da8, receiver=0x9f6e180, e=0xbfee7a8c) at kernel/qapplication.cpp:3862
#31 0x010a593a in KApplication::notify (this=0xbfee7da8, receiver=0x9f6e180, event=0xbfee7a8c) at ../../kdeui/kernel/kapplication.cpp:311
#32 0x0096f0bb in QCoreApplication::notifyInternal (this=0xbfee7da8, receiver=0x9f6e180, event=0xbfee7a8c) at kernel/qcoreapplication.cpp:731
#33 0x0099f1e4 in sendEvent (this=0x8e8d6a4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#34 QTimerInfoList::activateTimers (this=0x8e8d6a4) at kernel/qeventdispatcher_unix.cpp:604
#35 0x0099bdf4 in timerSourceDispatch (source=0x8e8d670) at kernel/qeventdispatcher_glib.cpp:184
#36 0x019c2aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#37 0x019c3270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#38 0x019c3524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#39 0x0099c53c in QEventDispatcherGlib::processEvents (this=0x8e4b748, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#40 0x069bd1e5 in QGuiEventDispatcherGlib::processEvents (this=0x8e4b748, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#41 0x0096e289 in QEventLoop::processEvents (this=0xbfee7d24, flags=...) at kernel/qeventloop.cpp:149
#42 0x0096e522 in QEventLoop::exec (this=0xbfee7d24, flags=...) at kernel/qeventloop.cpp:201
#43 0x00972ecc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#44 0x069048e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#45 0x0804f1b1 in main (argc=167604, argv=0x90a23a0) at ../../../akregator/src/main.cpp:103

Possible duplicates by query: bug 280257, bug 271386, bug 268593.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-08-28 17:41:43 UTC

*** This bug has been marked as a duplicate of bug 163573 ***
Comment 2 Joshua J. Kugler 2011-08-28 20:23:16 UTC
Could you please provide an explanation?  This bug has been resolved as a duplicate of a bug that was closed over three years ago.  If it is still appearing, how can it be a duplicate of a closed bug?
Comment 3 Christophe Marin 2011-08-28 21:03:10 UTC
hm? bug 163573 is still opened
Comment 4 Joshua J. Kugler 2011-08-28 21:09:02 UTC
(In reply to comment #3)
> hm? bug 163573 is still opened

Sigh...chalk one up to reading too fast (or not reading). I saw "resolved" on the bug marked duplicate, and didn't read the "NEW" status on 163573. Sorry about that.

A little more context on my report(s): after restarting Akregator a few times, it finally stopped crashing, and I've been using it for a while now with no new crashes.  When it first started crashing, it was reading files from an old version of Akregator (KDE 3.5.x).  Maybe once it "upgraded" everything, it was all OK.