Number of unread messages reverts back to previous value when Mozilla is started

RESOLVED EXPIRED

Status

MailNews Core
Database
--
minor
RESOLVED EXPIRED
15 years ago
10 years ago

People

(Reporter: Jonas Otter, Assigned: Bienvenu)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

When Mozilla Mail is restarted after being closed down, the number of unread
messages reported reverts back to some old state from the previous session, e.g.
from 89 to 228 unread messages. Also the corresponding number of messages revert
back to unread status. My mailboxes are stored on a FAT32 partition, so that I
can use Mozilla to read mail in both Windows and Linux on a double-boot machine,
that way all my mail can be seen from both OSes.

Reproducible: Sometimes

Steps to Reproduce:
1. Mark a number of messages unread
2. Shut down Mozilla
3. Start up Mozilla

Actual Results:  
See above, number of unread mails sometimes reverts back to the number before
step 1, some mail messages will be marked unread (those which were marked read
in step 1)

Expected Results:  
The same messages should have been read or unread after step 3 as before step 1,
i.e. I should not have to mark them all as read all over again.

Default theme
Mailboxes on a FAT 32 partition. I installed Mozilla under Windows first, then
rebooted into Linux and pointed the Linux Mozilla at the Windows directories so
as to pick up the mailbox from both OSes

Comment 1

14 years ago
See
http://bugzilla.mozilla.org/show_bug.cgi?id=171110#c9

If that's not it, here are some more to look at:
bug 66239
bug 159267
bug 195787
bug 221345
bug 224442
bug 224686
Product: MailNews → Core
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.