Closed
Bug 693575
Opened 13 years ago
Closed 13 years ago
Search folder (searching newsgroups) marks things unread
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 695309
People
(Reporter: henrik.lindberg.private, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/534.50.2 (KHTML, like Gecko) Version/5.0.6 Safari/533.22.3
Steps to reproduce:
I have a search folder that searches for keywords in subject and body of 3 gmane newsgroups (gmane.comp.sysutils.puppet.user, ...devel, and ...bugs). The search folder is placed under a local folder.
Actual results:
Read messages are shown as unread in the message list. (Often the first message in a thread).
The Search folder is in bold, and shows an unread count (that is not correct).
Visiting the messages marks them as unread - sometimes the unread count on the folder does not update.
After having visited all "unread" in the folder, and doing something else for a while, the messages again show up as unread.
Expected results:
Read messages should stay unread, and the unread count of the search folder should stay in sync with the number of unread messages.
Comment 1•13 years ago
|
||
(In reply to Henrik Lindberg from comment #0)
Probably similar to bug 372372.
Comment 2•13 years ago
|
||
Henrik does this happens in -safe-mode too ?
Reporter | ||
Comment 3•13 years ago
|
||
Have not tried with -safe-mode
I wonder if the problem is also related to bug 695309 where a probable cause could be issues with queuing and connections. That bug often causes all NNTP messages to be marked as unread. Until that issue is solved, this issue has very small chances of being fixed.
Comment 4•13 years ago
|
||
If this first appeared in version 8, then this is almost certainly another copy of bug 695309.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 5•12 years ago
|
||
Happens again for me in TB 17.0.2.
You need to log in
before you can comment on or make changes to this bug.
Description
•