Summary: | Items marked as read when fetching new feeds | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Alejandro Exojo <suy> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | dev+kde, graham.anderson |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alejandro Exojo
2007-06-14 11:15:34 UTC
FWIW, I want to add that I downgraded only akregator to 3.5.6, and since then, I don't lose feeds. :) Regards. I too have a problem where items are wrongly marked as read. It seems to happen to random entries. One of the triggers seems to be restarting akgregator, either from a complete close or from kde's sessesion restore - but it happens at other times too. I have a large archive and over a hundred unread articles (which makes it particularly annoying when the articles that disappear are part of the backlog). I'd like to get to the bottom of this, if possible. I'm having the same problem with KDE 3.5.8, akregator 1.2.7, on my ubuntu machine. This is especially annoying, as I depend on the unread items for future reference. Same as Imri, I do have the problem on Kubuntu 7.10, using Akregator 1.2.7 on KDE 3.5.8 It's a simple thing, but it's quite annoying. Even if I change the read items as unread (as they are supposed to be) they keep changing. This bug is still plagues Akgregator and we are now on 1.5.1 in KDE 4.3.1 Hi. I've tried to reproduce this bug in a recent akregator version (4.4 branch) and I could not reproduce it. I don't know if it's gone for sure, so it will be nice if somebody can comment on it too. Thanks. Hi. I've tried to reproduce this bug in a recent akregator version (4.4 branch) and I could not reproduce it. I don't know if it's gone for sure, so it will be nice if somebody can comment on it too. Thanks. This bug still remains in the 4.4.3 release. I can reproduce it at will. 1. Select a feed with new entries 2. Select "fetch all feeds" 3. Watch existing unread entries get marked as read. It happens also on every automatic fetch of feed updates. *** Bug 161350 has been marked as a duplicate of this bug. *** I too reported this problem in 2008, but haven't had it for a long time now. How about you others? Would you consider it fixed? Let's close this report then. Thanks for the feedback. |