Bug 220084 - akregator crash due to unknown reason
Summary: akregator crash due to unknown reason
Status: RESOLVED DUPLICATE of bug 116482
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: 2009-12-25 20:07 UTC by vegeta
Modified: 2010-01-01 13:02 UTC (History)
0 users

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 vegeta 2009-12-25 20:07:17 UTC
Application that crashed: akregator
Version of the application: 1.5.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.6-166.fc12.i686.PAE i686
Distribution: "Fedora release 12 (Constantine)"

What I was doing when the application crashed:
i dont understand the reason

 -- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[KCrash Handler]
#6  0x0034afa6 in memcpy () from /lib/libc.so.6
#7  0xbf9aaa18 in ?? ()
#8  0x036f59c7 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#9  0x036ec400 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#10 0x036efe1f in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#11 0x036f4f2b in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#12 0x037009f7 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#13 0x0370372f in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#14 0x0553aea8 in Akregator::Feed::loadArticles() () from /usr/lib/kde4/akregatorpart.so
#15 0x0553ed94 in Akregator::Feed::fromOPML(QDomElement, Akregator::Backend::Storage*) () from /usr/lib/kde4/akregatorpart.so
#16 0x0554a360 in Akregator::FeedList::parseChildNodes(QDomNode&, Akregator::Folder*) () from /usr/lib/kde4/akregatorpart.so
#17 0x0554a57e in Akregator::FeedList::parseChildNodes(QDomNode&, Akregator::Folder*) () from /usr/lib/kde4/akregatorpart.so
#18 0x0554bd7c in Akregator::FeedList::readFromOpml(QDomDocument const&) () from /usr/lib/kde4/akregatorpart.so
#19 0x05590999 in ?? () from /usr/lib/kde4/akregatorpart.so
#20 0x055914ea in ?? () from /usr/lib/kde4/akregatorpart.so
#21 0x05591923 in ?? () from /usr/lib/kde4/akregatorpart.so
#22 0x02153c0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#23 0x02154843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#24 0x02158cf8 in ?? () from /usr/lib/libQtCore.so.4
#25 0x02158e1d in ?? () from /usr/lib/libQtCore.so.4
#26 0x0214dd3f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#27 0x05e7fb24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#28 0x05e87281 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#29 0x06ec702b in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#30 0x0213dd73 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#31 0x0216b2be in ?? () from /usr/lib/libQtCore.so.4
#32 0x02168c21 in ?? () from /usr/lib/libQtCore.so.4
#33 0x00a27128 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0x00a2aa58 in ?? () from /lib/libglib-2.0.so.0
#35 0x00a2ab84 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0x02168b6d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#37 0x05f1f356 in ?? () from /usr/lib/libQtGui.so.4
#38 0x0213c2aa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#39 0x0213c70a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#40 0x0213ebf7 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#41 0x05e7f9a8 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#42 0x0804f189 in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2010-01-01 13:02:06 UTC

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