Closed Bug 539035 Opened 16 years ago Closed 16 years ago

Erratic and inconsistent display of starred messages

Categories

(MailNews Core :: Backend, defect)

1.9.1 Branch
x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 540554

People

(Reporter: bugzilla, Unassigned)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 I have used TB2 for some time and everything worked well. I recently did a complete reinstall of Windows and installed TB3. I use TB to access an IMAP email acocunt from Fastmail. Emails are moved (both automatically and manually) into different folders and I use the ability to star messages to indicate when I have finished working on an email. Non-Starred messages are then collected in a number of Saved Searches to be worked on. Since the first installation of TB3 messages that have been correctly starred have suddenly appeared as non-starred, sometimes this is a few random emails, but most times it is 20-30+ emails from the same folder that appear as non-starred. After some time the problem will correct itself if I ignore it. The most recent occurrence of this resulted in about 40 messages that had been previously starred (some many months ago) appearing in TB as non-starred. However all of these was still correctly flagged (starred) on the Fastmail web interface. As a test I then rebuilt the index for the folder that was affected and the emails returned to being correctly starred. (Folder propertied -> Rebuld Index). Reproducible: Sometimes
Version: unspecified → 3.0
So it sounds like a corruption of the local DB with upadte of FLAGS over imap. Are you running extensions ? (can you disable them and see if your issue is still present) Would be nice to have clearer and simpler steps to reproduce.
Component: General → Backend
Keywords: regression
Product: Thunderbird → MailNews Core
QA Contact: general → backend
Version: 3.0 → 1.9.1 Branch
The only extension I was running was the British English Dictionary. I disabled that earlier today and the problem has just happened again. It is very difficult to give clear/simple steps to reproduce as this error seems erratic. I have no idea when it will happen and when it does I have discovered that I can correct it by rebuilding the index for the affected folder, of I can wait and persumably next time TB reindexes the folder the problem disappears. Let me know if I can help with any other info, or if there is anything else I can try to diagnose the problem better.
This sounds like an other manifestation of the condstore issues we've been seeing. You might try a 3.01 candidate build from here - http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/3.0.1-candidates/build1/ If this is a condstore issue, I believe turning off the use of condstore might help - https://bugzilla.mozilla.org/show_bug.cgi?id=530551#c3, or you could try generating an imap protocol log when this happens and sending me a log https://wiki.mozilla.org/MailNews:Logging - bienvenu@mozillamessaging.com
Status: UNCONFIRMED → NEW
Ever confirmed: true
David, I upgraded to 3.0.1 and this made no difference. In fact it made things worse as many messages appeared as unread as well as not-starred! I have now turned off the use of condstore and that seems to have resolved the problem. I will update this ticket in a few more days when I am confident that the problem has not re-appeared. Sandy
Sandy, you could turn condstore back on and try a build with a fix for this bug - http://s3.mozillamessaging.com/build/try-server/2010-01-20_15:30-bienvenu@nventure.com-1264029848/bienvenu@nventure.com-1264029848-mail-try-win32.installer.exe It's basically 3.01 plus a bug fix. If you do try it, and it helps, please let us know. (or you could just leave condstore support off).
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
The build above is installed and condstore turned back on. I will test and let you know.
I have been using this build now for two days and it seems to have fixed the problems. Condstore is turned back on and I have had no re-occurance of the problems. Many thanks for this bugfix.
thx for the feedback, Sandy.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.