Bug 196633 - old entries reloaded as new ones (doubled entries)
Summary: old entries reloaded as new ones (doubled entries)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-15 16:46 UTC by Maciej Pilichowski
Modified: 2017-01-07 22:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2009-06-15 16:46:50 UTC 
Version:            (using KDE 4.2.90)
Installed from:    SuSE RPMs

What I did (akregator starts with KDE)
a) started computer + KDE
b) switched to text console
c) switched back to KDE
d) logged out
e) logged in
f) restarted computer

And when KDE started I get around 262 new messages (it should be 1). Simply akregator refetched a lot of old news from various feeds as new ones. The one feed is created by me, and it is static file (not auto-generated) and it was last changed ~1.5 month ago.
Comment 1 Frank Osterfeld 2009-06-27 22:42:24 UTC 
Did you update kdepim and/or akregator between the Akregator starts?
Comment 2 Maciej Pilichowski 2009-06-28 08:00:17 UTC 
No. 

Btw. I am not saying it happens all the time, I guess I hit by accident some weak spot inside akregator (maybe I logout while akregator was fetching data and something broke).
Comment 3 Dominik Stadler 2009-11-05 00:35:04 UTC 
Sounds related to Bug 210408, Bug 199232 and bug 185507.
Comment 4 Denis Kurz 2016-09-24 19:39:56 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 5 Denis Kurz 2017-01-07 22:25:21 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.