Version: (using KDE KDE 3.3.1) Installed from: Debian testing/unstable Packages When I configure akregator in way that for example not more than 5 news a kept, then I happens that feeds how don't have much news (like tikiwiki.org) keep fetching old news again after there are deleted because of expiring. So there should be a kind of database knowing that a news allready has been shown, even though its not in the kept anymore.
To prevent this, akregator must save the guid/hash of the deleted feeds until they aren't in the feed source anymore.
Some feeds (such as default "Akregator news") keep fetching again after startup even if they are deleted manually.
Maxim: you mean you delete the "Akregator news" _feed_ from the feed tree but it's "Akregator news" is fetched afterwards? Does this also happen after restart?? Could you explain the steps how to reproduce it?
I think I found out what Maxim wants to say. I can reproduce it here for Akregator 1.0 (Using KDE 3.4.0 Level "a" SUSE LINUX 9.2 UNSUPPORTED) Steps to reproduce: 1. Add the feed "Akregator News": http://akregator.sf.net/rss2.php 2. Now delete an entry from the article list of this article (which one does not seem to be of importance) 3. Quit Akregator (do not minimize it to tray) 4. Restart Akregator and wait until the feed gets fetched again (or fetch it manually). Results: - After restarting Akregator the deleted entry reappears in the article list (marked as new) Expected results: - The article should not appear in the list anymore.
This is fixed in HEAD. For 3.4 branch, I consider it as WONTFIX.