Bug 321549 - akregator miscalculates the total number of messages
Summary: akregator miscalculates the total number of messages
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.11 beta1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-24 09:34 UTC by qqqqqqqqq9
Modified: 2017-01-07 22:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
illustration of miscalculation 8+1 equals 9 not 8 (91.02 KB, image/png)
2013-06-24 09:45 UTC, qqqqqqqqq9 		Details
Content of heise-Feed (61.27 KB, image/png)
2013-06-24 09:46 UTC, qqqqqqqqq9 		Details
new message not recognised as unread (75.70 KB, image/png)
2013-06-24 09:47 UTC, qqqqqqqqq9 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description qqqqqqqqq9 2013-06-24 09:34:22 UTC 
akregator seems to ignore feeds which contain only new messages in the calculation of the total number of unread messages

Reproducible: Always

Steps to Reproduce:
1. please look at the screenshots.
2.
3.
Actual Results:  
 please look at the screenshots.

Expected Results:  
 please look at the screenshots.
Comment 1 qqqqqqqqq9 2013-06-24 09:45:53 UTC 
Created attachment 80742 [details]
illustration of miscalculation 8+1 equals 9 not 8
Comment 2 qqqqqqqqq9 2013-06-24 09:46:38 UTC 
Created attachment 80743 [details]
Content of heise-Feed
Comment 3 qqqqqqqqq9 2013-06-24 09:47:33 UTC 
Created attachment 80744 [details]
new message not recognised as unread
Comment 4 Denis Kurz 2016-09-24 19:43:11 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 5 Denis Kurz 2017-01-07 22:39:47 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.