Summary: | old entries reloaded as new ones (doubled entries) | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Maciej Pilichowski <bluedzins> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | dominik.stadler, osterfeld |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Maciej Pilichowski
2009-06-15 16:46:50 UTC
Did you update kdepim and/or akregator between the Akregator starts? 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). Sounds related to Bug 210408, Bug 199232 and bug 185507. 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. 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. |