Closed Bug 1227878 Opened 10 years ago Closed 1 year ago

saved search / virtual folder with online search enabled only shows new messages

Categories

(Thunderbird :: Search, defect)

42 Branch
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 365392

People

(Reporter: martin.monperrus, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20151029151421 Steps to reproduce: I refresh a virtual saved search / virtual folder with online search enabled where the search criteria is Status=unread (IMAP, with Synchro, mailbox, idle=false,condstore=false) Actual results: Only the new messages on server are shown Expected results: All unread messages should be shown
Component: Untriaged → Search
monperrus, still seeing this issue?
Flags: needinfo?(martin.monperrus)
Whiteboard: [closeme 2018-01-20]
yes, I have just reproduced it a number of times with TB58, but not deterministically. I'm now trying to identify the exact sequence of actions to reproduce the bug.
Flags: needinfo?(martin.monperrus)
Steps to reproduce: 1) create a virtual saved search / virtual folder, say "vsearch", with online search enabled where the search criteria is Status=unread, saved under the IMAP account => the unread count is correct 2) select "vsearch" in ui 3) send an email to this account 4) refresh => the unread count is correct (unread + 1) 5) move to folder up (in my case "Trash) 6) move again to "vsearch", one folder down => the unread count becomes 1 (only the new message), **incorrect** 7) move to folder up (in my case "Trash) 8) move again to "vsearch", one folder down => the unread count becomes correct again with all unread messages Notes: the bug also happens with IDLE=true (step 4 is automated then), and is independent from the status of use_condstore
Note that this reproduction scenario is quite close to the workaround discussed in bug 365392, which may be a duplicate.
Whiteboard: [closeme 2018-01-20]
Severity: normal → S3
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 365392
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.