298188 - 'Mark newgroup read' doesn't.

Status: RESOLVED EXPIRED

(MailNews Core :: Database, defect)

Description

[walter sheets]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050618 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050618 Firefox/1.0+

Applies to mozilla(HEAD) and thunderbird(HEAD):
When examining a news account, the number of articles in each newsgroup is
updated automatically, of course.

The problem occurs when I right-click on a newsgroup and then click on 'Mark
newsgroup read'.  Everything seems fine until the next time I open that same
news account and see that all those thousands of articles are back again, just
as if I had never marked them as 'read'.

Reproducible: Always

Steps to Reproduce:
1.In the Folders pane, click on a News account to show all the subscribed groups.
2.Right-click on any group and select 'Mark newsgroup read'.
3.Close the program (optional) and then re-check the same newsgroup.

Actual Results:  
All the news articles are still 'unread'.

Expected Results:  
There should be zero articles waiting to be read in that newsgroup.

Comment 1

[walter sheets]

Very important addendum:  this bug only happens in a newly-subscribed newsgroup
which has never been read before.  This is particularly confusing when importing
your mozilla mail/news settings into a fresh thunderbird install.

Comment 2

[Andrew Schultz]

I've seen this before, but don't know how to cause it.  I eventually break down
and unsubscribe/resubscribe to the newsgroups and things work again.  I guess
there should at least be a better way to clean up when things get corrupted. 
Might be related to bug 271537.

dumping in mail database

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.