Bug 230286 - count of unread messages in akregator is -1
Summary: count of unread messages in akregator is -1
Status: RESOLVED DUPLICATE of bug 173090
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-11 01:51 UTC by meyerm
Modified: 2010-03-25 23:52 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description meyerm 2010-03-11 01:51:56 UTC
Version:           1.6.1 (using 4.4.1 (KDE 4.4.1), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.33-gentoo

Sorry for this undetailed report. But I have no idea how to reproduce this.

It just happened to me that I got an "unread" count of -1 in one of my feeds (which got propagated all the tree up to "All Feeds"). In the feed folder where the count was -1 there was only one unread message (so the counter should have been 1 and not -1). The message was not readable after clicking on it. I changed the filter from "unread" to "All Articles" but this specific message was not reable even after first clicking on other messages. BTW: It looks like it has a title, an author and a time, but no date.

I still have this message in the list, so if you want me to do sth. with it, just ask.
Comment 1 meyerm 2010-03-11 01:55:53 UTC
I  just changed my settings from "delete messages after 30 days" to "keep them forever" so this message won't get deleted. I don't know if this is related. Buuut:

After I clicked on All Feeds and left the sub folder with this specific feed Akregator/Kontact crashed. Unfortunately I just started keeping debug symbols and haven't recompiled KDE since then. So there was no usable backtrace.
Comment 2 Christophe Marin 2010-03-25 23:52:10 UTC

*** This bug has been marked as a duplicate of bug 173090 ***