Issues with akregator

[Bjarne Wichmann Petersen]

Hi

I've recently switched from FreeBSD to Kubuntu and I'm having some issues with 
aKregator.

On FreeBSD aKregator was a great tool, but I'm finding it less than useful on 
Kubuntu (though it shouldn't be, aKregator should be identical on both 
platforms).

Issue 1. On FreeBSD aKregator would remember you last "status"-setting (all, 
new, unread or important) when startet. Now it's always on "all". And when 
fetching new stories it would update the view, so when set on "unread" it 
would really only display unread stories instead of 
unread-since-I-last-changed-the-status-setting. And now I'll have to change 
it into something else and then back to unread. That is a bit annoying.

Issue 2. The archive/filtering seems a lot less effective than on FreeBSD. 
Many stories will (on Kubuntu) when flagged "read" reappear as "new/unread" 
after the next fetch-cycle. On FreeBSD it was usually only the Groklaw-feed 
that would mess around. I've set the archive-size to 1000 and fetch around 
2-300 stories a day (just copied the settings from FreeBSD).

Is it possible to resolve those 2 issues and get back to the "old" FreeBSD 
behavior?

Issue 3. It looks like a little bug have introduced itself with the upgrade to 
3.5.2. When I start aKregator inside Kontact I get an error-message that 
Kontact is already running and whether or not I'd like to force access to the 
Archive.

Bjarne