Bug 304919 - Folder unread message count incorrect, leads to crash
Summary: Folder unread message count incorrect, leads to crash
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-10 10:14 UTC by Brendan McKenna
Modified: 2017-01-07 21:53 UTC (History)
0 users

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


Attachments
Screenshot showing symptoms of problem. (146.63 KB, image/png)
2012-08-10 10:14 UTC, Brendan McKenna
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brendan McKenna 2012-08-10 10:14:48 UTC
Created attachment 73085 [details]
Screenshot showing symptoms of problem.

Using Akregator 4.7.2, "release 5" on an openSuSE system that reports the following from a uname -a:

Linux gallifrey 3.1.10-1.16-desktop #1 SMP PREEMPT Wed Jun 27 05:21:40 UTC 2012 (d016078) x86_64 x86_64 x86_64 GNU/Linux

Folders report an incorrect number of unread messages, in some cases reporting no unread messages in a folder when the feeds (correctly) show unread messages, in others the number of messages in the folder is correct but the totals from subfolders are incorrectly aggregated.

In many cases, continuing to use the application leads to a crash with a segmentation fault.  A restart of the application does sometimes clear the problem, but it frequently reappears the first subsequent fetch.

Fairly reproducable.  See attached screenshot for the symptoms.
Comment 1 Denis Kurz 2016-09-24 19:45:33 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:53:21 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.