Number of unread messages displayed wrong after deleting and recreating folder
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: commerce, Unassigned)
References
(Blocks 1 open bug)
Details
Comment 1•18 years ago
|
||
Updated•16 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #2)
TCW can you reproduce this?
Nope. After the STR and then deleting and re-creating the folder, it's empty and no unread messages listed in braces or bold.
Comment 4•2 years ago
|
||
I just reproduced it following the STR with Thunderbird 102.4.2 on Ubuntu.
I was able to reproduce it with a local folder, with a POP-account folder, and with an IMAP account folder.
Comment 5•2 years ago
|
||
(In reply to B.J. Herbison from comment #4)
I just reproduced it following the STR with Thunderbird 102.4.2 on Ubuntu.
I was able to reproduce it with a local folder, with a POP-account folder, and with an IMAP account folder.
Hmm, I am using 108.0b1 but I am Windows 10. Maybe it's still a Linux thing?
Comment 6•2 years ago
|
||
I just installed 108.0b1 and can still reproduce the issue. It does seem OS related.
Comment 7•2 years ago
|
||
(In reply to B.J. Herbison from comment #6)
I just installed 108.0b1 and can still reproduce the issue. It does seem OS related.
Anything interesting in Error Console when doing the STR?
Comment 8•2 years ago
|
||
In step 5, I created the new local folder and the name appeared bold and with the incorrect (1). About three or four seconds later a message appeared in the console:
gloda.index_msg: Exception while attempting to mark message with gloda state afterdb commit
Exception { name: "NS_ERROR_ILLEGAL_VALUE", message: "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBHdr.getUint32Property]", result: 2147942487, filename: "resource:///modules/gloda/IndexMsg.jsm", lineNumber: 159, columnNumber: 0, data: null, stack: "_commitCallback@resource:///modules/gloda/IndexMsg.jsm:159:33\nhandleCompletion@resource:///modules/gloda/GlodaDatastore.jsm:65:11\n", location: XPCWrappedNative_NoHelper }
IndexMsg.jsm:178:30
I repeated the experiment and the same thing happened (including the same result value). This is with 108.0b1.
Comment 10•11 months ago
|
||
I just reproduced the issue with 122.0b4.
One difference: I didn't see any messages in the error console.
Description
•