Bug 161313

Summary: Feed lists contents are corrupted
Product: [Applications] akregator Reporter: Heiko Nock <hnock>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: major CC: christophe, frank, guillaume.theyssier, kde, lacsilva, osterfeld
Priority: NOR    
Version: 4.11.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot of the problem
Another screenshot of the problem
new screenshot showing the problem

Description Heiko Nock 2008-04-26 22:27:35 UTC
Version:           1.2.9 (using 3.5.9, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.25-gentoo

I've been having this problem for months, but I thought it would be fixed eventually. However, after several updates to KDE, Akregator's behaviour still hasn't changed in 2.5.9.

I have a very long list of 266 feeds, mostly podcasts.

The problem is that the feed lists behave completely unpredictable:

1. Unread entries are sometimes marked as read although they haven't been opened yet. 

2. In the same way read articles are sometimes marked as unread. There doesn't even seem to be a noticeable pattern when this happens. The result is a feed list with corrupted content that doesn't reliably show which entries have already been accessed and which haven't. 

On rare occasions entries from one feed suddenly appeared as copies in a completely different feed. 

For example in the feed list for
http://myextralife.com/ftp/radio/rss.xml
I also have copies of almost all entries from a completely different podcast at 
http://mdm.podspot.de/rss+all

I suspect that Akregator has a problem with the amount of feed lists and the overall amount of feed list entries. I didn't have problems like that when I started out using Akregator. The problems showed up a few weeks after adding feed lists.
Comment 1 Thomas McGuire 2008-05-04 14:05:11 UTC
I have the same problem in trunk.
Some articles appear in another, unrelated feed, and many articles in one feed are marked as unread again when fetching the feed.
This makes Akregator unusable for me.
Comment 2 Thomas McGuire 2008-05-04 14:09:08 UTC
Created attachment 24625 [details]
Screenshot of the problem

In this screenshot, you'll see the problem.
The feed from Jaroslaw contains several articles by Andreas. The author
information in the article list is incorrect (and contains HTML code, which
shouldn't be there). The author information in the article display is correct.
Comment 3 Daniel Winter 2008-05-05 08:32:31 UTC
I have the same problem with random messages from some feeds show up under others feeds as duplicates
Comment 4 Michał ,,KNT'' Gorycki 2008-05-11 11:48:11 UTC
Created attachment 24705 [details]
Another screenshot of the problem
Comment 5 Michał ,,KNT'' Gorycki 2008-05-11 11:50:47 UTC
I have the same problem with entries marked unread for 1.2.9 (KDE 3.5.9) for Debian testing/unstable.
I've also attached a screenshot. It even marks a case when I've manually set the entries as new yesterday.
Comment 6 Guillaume THEYSSIER 2008-09-04 15:12:16 UTC
Same problem of old messages from one feed appearing duplicated and marked unread in another one.
akregator 1.2.7
Comment 7 Luis Silva 2008-11-23 17:53:55 UTC
i cannot reproduce this with:
Version 1.3.3
Using KDE 4.1.3 (KDE 4.1.3)
Comment 8 Frank Osterfeld 2009-01-10 18:27:34 UTC
Can anyone reproduce this with >= 4.1.2? 
Comment 9 Christophe Marin 2009-03-08 21:19:41 UTC
No feedback for ~2 monthes (see comment #8). Closing this bug report.
Comment 10 Frank Niethardt 2010-03-25 10:08:17 UTC
I have the problem from time to time, too. Today it happened again.

Archlinux, KDEmod 4.4.1, Akregator 1.6.1
Comment 11 Frank Niethardt 2010-03-25 10:10:29 UTC
Created attachment 42247 [details]
new screenshot showing the problem

As you can see, Dilbert in the middle of another feed...
Comment 12 Rolf Eike Beer 2012-08-17 16:17:31 UTC
Hit it today, using 4.8.5.
Comment 13 Rolf Eike Beer 2013-09-13 03:13:30 UTC
Still happens in 4.11.1.
Comment 14 Denis Kurz 2016-09-24 19:44:02 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 15 Denis Kurz 2017-01-07 22:30:19 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.