Bug 167901

Summary: Scrolling through the articles with shortcut "previous unread article" doesn't change unread count
Product: [Applications] akregator Reporter: Joonas Koivunen <joonas.koivunen>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Joonas Koivunen 2008-07-31 22:06:16 UTC
Version:           1.2.50 (using 4.1.00 (KDE 4.1.0), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-19-generic

1. Open a feed "Planet KDE" (one of the default KDE feeds)
 2. Quickly repressing shortcut for "Previous unread article" (- for minus)
 3. Moving to an article does turn the boldness of the article row to regular but doesn't change Unread -count on the left pane

This does seem to happen only with "KDE Dot News" (http://www.kde.org/dotkdeorg.rdf) and "Planet KDE" (http://planetkde.org/rss20.xml).

For "Akregator News" (http://akregator.sf.net/rss2.php) this works as expected (unread count goes down as you move through the articles).

Not even right clicking "Planet KDE" > "Mark feed as read" change the unread count.

Now that I restarted the application it works as expected, "unread" cells have the correct value. After the restart even "Planet KDE" seems to work again.

This could be a result of a previous crash that happened after I imported by old feeds from akregator-kde3.
Comment 1 Denis Kurz 2016-09-24 19:40:40 UTC
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.
Comment 2 Denis Kurz 2017-01-07 21:52:27 UTC
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.