Bug 321637 - duplicate entries displayed after the refresh of the current feed channel
Summary: duplicate entries displayed after the refresh of the current feed channel
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.11 beta1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-26 14:20 UTC by Kapcsándi István
Modified: 2017-01-07 22:47 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 Kapcsándi István 2013-06-26 14:20:52 UTC
Duplicate entries are displayed when I (or the autorefresher) do refresh the current feed channel.
If I navigate to another feed and then I come back the duplicates are vanished.



Reproducible: Always

Steps to Reproduce:
1. add - if not yet added - a feed which has frequent updates, eg.: http://9gagrss.com/feed/
2. 'read' it for a while, scroll down ..
3. hit F5 (refresh) or - if you have set auto refresh read more
4. when the refresh happen, the feed jumps to the top - and the new posts are duplicated. Every new post displayed twice.
5. navigate/click to another feed
6. navigate/click back to the previous feed. The duplicate entries are gone.
Actual Results:  
I see duplicate entries at step 4.

Expected Results:  
I do not see duplicates, only single post, just like at step 6.

I'ts not a 'new' bug, I see this since, ... I swiched from google reader last year.
Comment 1 Denis Kurz 2016-09-24 19:38:29 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 2 Denis Kurz 2017-01-07 22:47:11 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.