Message couldn't be deleted (Component returned failure code: 0x80550018 [nsITreeView.isContainer])
Categories
(Thunderbird :: Message Reader UI, defect)
Tracking
(thunderbird_esr91 unaffected, thunderbird112 affected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr91 | --- | unaffected |
| thunderbird112 | --- | affected |
People
(Reporter: soeren.hentzschel, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: dupeme, Whiteboard: [Supernova3p])
STR:
Unfortunately no steps to reproduce since it only happened once. I deleted some messages from the junk folder of my Yahoo Mail account. This worked for every message but the last one - at least it seemed so. The console showed the following error:
Exception
columnNumber: 0
data: null
filename: "chrome://messenger/content/tree-view.mjs"
lineNumber: 167
location: XPCWrappedNative_NoHelper { QueryInterface: QueryInterface(), filename: Getter, name: Getter, … }
message: "Component returned failure code: 0x80550018 [nsITreeView.isContainer]"
name: ""
result: 2153054232
stack: "handleEvent@chrome://messenger/content/tree-view.mjs:167:24\n"
The same error appeared every time I tried to delete the message until I restarted Thunderbird. After the restart the message was no longer there. So I guess the message was in fact already deleted after the first try but the UI was no longer in sync with the reality.
Thunderbird Daily 112.0a1 (2023-03-07) on macOS 13.2.1.
|
||
Comment 1•2 years ago
|
||
Based on the description, I would expect this to be a duplicate of an existing bug
|
||
Comment 2•2 years ago
|
||
Something similar happened to me while I had issues with message list not updated after delete.
To me, it seems that the error root is what is shown in the Message list UI is wrong, so TB return an error and can't perform the action. That's why restarting solve the issue. Switching and coming back to the same folder sole it too.
It might be a duplicate of bug 1817878. Soren, what do you think ?
|
Reporter | |
Comment 3•2 years ago
•
|
||
I can't see any mention of a message that couldn't be deleted in bug bug 1817878 nor was the same error message mentioned there. So even if it has the same root cause it's something the developers have to figure out, I can't answer that.
|
|
||
Updated•2 years ago
|
|
|
Reporter | |
Comment 4•2 years ago
|
||
I didn't see this for a while.
Description
•