Akregator Problem

I'm using 11.2 with kde 4.3.5 release 0 and have Akregator installed. It crashed occasionally, but this didn't worry me too much, as I know that a patch will come along eventually.

However, an automatic update came along about 2 weeks ago and this makes it crash on program startup. I think the update was libpython -(but I am not sure).

I would like to fix this (even though the new version is due soon) and would like to know if it is possible to identify the update in question or how can I check and fix compatability with other programs.

Here is he log :
Application: Akregator (akregator), signal: Segmentation fault
[KCrash Handler]
#5 0x00007f33136e171b in memcpy () from /lib64/libc.so.6
#6 0x00007f3305fc4440 in QString::free(QString::Data*) () from /usr/lib64/kde4/akregator_mk4storage_plugin.so
#7 0x00007f3305fbbfe2 in QString::free(QString::Data*) () from /usr/lib64/kde4/akregator_mk4storage_plugin.so
#8 0x00007f3305fbf470 in QString::free(QString::Data*) () from /usr/lib64/kde4/akregator_mk4storage_plugin.so
#9 0x00007f3305fce6cb in QString::free(QString::Data*) () from /usr/lib64/kde4/akregator_mk4storage_plugin.so
#10 0x00007f3305fd119d in QString::free(QString::Data*) () from /usr/lib64/kde4/akregator_mk4storage_plugin.so
#11 0x00007f3305fd176d in QString::free(QString::Data*) () from /usr/lib64/kde4/akregator_mk4storage_plugin.so
#12 0x00007f3307d620ac in Akregator::Feed::loadArticles() () from /usr/lib64/kde4/akregatorpart.so
#13 0x00007f3307d65bf4 in Akregator::Feed::fromOPML(QDomElement, Akregator::Backend::Storage*) () from /usr/lib64/kde4/akregatorpart.so
#14 0x00007f3307d707bf in Akregator::FeedList::parseChildNodes(QDomNode&, Akregator::Folder*) () from /usr/lib64/kde4/akregatorpart.so
#15 0x00007f3307d709f6 in Akregator::FeedList::parseChildNodes(QDomNode&, Akregator::Folder*) () from /usr/lib64/kde4/akregatorpart.so
#16 0x00007f3307d709f6 in Akregator::FeedList::parseChildNodes(QDomNode&, Akregator::Folder*) () from /usr/lib64/kde4/akregatorpart.so
#17 0x00007f3307d72116 in Akregator::FeedList::readFromOpml(QDomDocument const&) () from /usr/lib64/kde4/akregatorpart.so
#18 0x00007f3307db081b in ?? () from /usr/lib64/kde4/akregatorpart.so
#19 0x00007f3307db12a3 in ?? () from /usr/lib64/kde4/akregatorpart.so
#20 0x00007f3307db1672 in ?? () from /usr/lib64/kde4/akregatorpart.so
#21 0x00007f3314bc9fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#22 0x00007f3314bcefff in ?? () from /usr/lib64/libQtCore.so.4
#23 0x00007f3314bc3f63 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#24 0x00007f33140802ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#25 0x00007f331408757e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#26 0x00007f33157a0016 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#27 0x00007f3314bb4ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#28 0x00007f3314be071d in ?? () from /usr/lib64/libQtCore.so.4
#29 0x00007f3314bdd678 in ?? () from /usr/lib64/libQtCore.so.4
#30 0x00007f330e39adee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#31 0x00007f330e39e7b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#32 0x00007f330e39e8e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#33 0x00007f3314bdd3a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#34 0x00007f331411331e in ?? () from /usr/lib64/libQtGui.so.4
#35 0x00007f3314bb3712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#36 0x00007f3314bb3ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#37 0x00007f3314bb5c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#38 0x00000000004095fd in _start ()

Seems to work from bottom up.

Akregator (or Kontact with Akregator incorporated) does crash now and then. IMHO this happens when for some reason the counter of unread items in a feed becomes negative. Now that is of course a strange thing of it's own. Often shortly after such a -n count Akregator crashes. There is this bug report about this.

It could also be your bug (not sure of course).

I assume the update you are talking about is one of the Security/Reccomended ones that are signalled by the Applett and are in the Update repos. When that is the case, I have it also installed (being up to date with those), but I did not found that Akregator crashes significantly more often then earlier. So this could be just happening.

Quote :

I assume the update you are talking about is one of the Security/Reccomended ones that are signalled by the Applett and are in the Update repos.

Yes this is the case.

Do you know of any way to reset the feed counter ?

Hi Henk
I think you are right about the counter. I removed akregator and the hidden akregator folder in ~ and then re-installed. All is OK now, except that I have to set the feeds up again,
Thanks for your help.
(Pity about the World Cup)

Hi Alastairo,

I am glad it helped. I never thought my story it would realy help (and wait for a few days to see if it comes back) except in giving more information, but I keep in mind that may be a delete of the directory in $HOME might help.

In my case, when a crash occurs and I then startup again, the negative count is gone and it runs happily on. The crash does happen onece every few days or so.

Oh, and do not worry about the Football thingy. I am not that interested in Football. I hope SA got something positive out of it.

Since I cleared out the .akregator info before re- installing, I have had no crashes and it works perfectly.
I only have a problem with this website (suseunbound) - where the articles downloaded to akregator are not in the normal form.

I have no problems getting the normal form of articles. I just received in Akregator your Crime question and it opens the normal web page.

I re-tried it now and it works perfectly. Must have been some unknown issue last time I tried. Thanks