Bug 445038 - Lost articles status when akregator is not closed ordered
Summary: Lost articles status when akregator is not closed ordered
Status: REPORTED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 5.18.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-05 19:05 UTC by Jaime Torres
Modified: 2021-11-05 19:05 UTC (History)
0 users

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 Jaime Torres 2021-11-05 19:05:57 UTC 
SUMMARY
When akregator is closed not in the right way, for example an interrupted session, a lot of already read articles are marked again as new, making it really hard to know which were already read.

EXPECTED RESULT
To lost as less articles states as possible. If I had only 10 new, after a session restore or not session restore, doesn't seem to matter, I can have more than 100 unread.

KDE Frameworks 
Version 5.87.0
Qt 
Version 5.15.2 (built against 5.15.2)