"open message in conversation" fails with error "Couldn't find a collection for msg: [xpconnect wrapped nsIMsgDBHdr] ConversationOpener.jsm:46:17"
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(thunderbird_esr102 unaffected)
Tracking | Status | |
---|---|---|
thunderbird_esr102 | --- | unaffected |
People
(Reporter: wsmwk, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [Supernova3p])
- Pick a message thread (perhaps one that has has messages in multiple folders - I'm not sure this is a required element)
- click a message and do open message in containing folder
- then do open message in conversation.
Nothing happens.
error console
Couldn't find a collection for msg: [xpconnect wrapped nsIMsgDBHdr] ConversationOpener.jsm:46:17
onQueryCompleted resource:///modules/ConversationOpener.jsm:46
_onQueryCompleted resource:///modules/gloda/Collection.jsm:681
onQueryCompleted resource:///modules/gloda/GlodaDatastore.jsm:169
handleCompletion resource:///modules/gloda/GlodaDatastore.jsm:450
Updated•2 years ago
|
Comment 1•2 years ago
•
|
||
(In reply to Wayne Mery (:wsmwk) from comment #0)
- Pick a message thread (perhaps one that has has messages in multiple folders - I'm not sure this is a required element)
- click a message and do open message in containing folder
- then do open message in conversation.
Wayne, can you clarify these steps? Open message in containing folder
is only available from search results but it's not mentioned in steps (looks like you've used global search, which has many ways of getting to a message list...). But then, your subsequent workflow (Open message in conversation
) is not clear as to where and why. Maybe I did it different, but I'm also failing to reproduce on 115.0a1 (2023-05-11) (64-bit) or 113.0b6 (64-bit), Win10.
Updated•2 years ago
|
Reporter | ||
Comment 2•2 years ago
|
||
I don't have a clarification at hand. I test one theory, but could not reproduce.
I'll try again later.
Comment 3•1 year ago
|
||
Opening in conversation and then in containing folder works fine here. So does the other way around. That error message usually means Gloda's indexing has stuffed up somewhere along the way, again.
Description
•