1558632 - can't undo ignore thread or ignore subthread

Status: RESOLVED DUPLICATE of bug 1565840

(Thunderbird :: Mail Window Front End, defect)

Description

[Jonathan Kamens]

Attempts to undo an ignore thread or ignore sub-thread, either with the menu or by typing k or shift-k, yields this:

An error occurred executing the cmd_killThread command: TypeError: this.notificationbox is undefined globalOverlay.js:83
goDoCommand chrome://global/content/globalOverlay.js:83
oncommand chrome://messenger/content/messenger.xul:1
An error occurred executing the cmd_killSubthread command: TypeError: this.notificationbox is undefined globalOverlay.js:83
goDoCommand chrome://global/content/globalOverlay.js:83
oncommand chrome://messenger/content/messenger.xul:1
uncaught exception: 2147746065 2 autosync.jsm:199:30

I ran a regression window with mozregression:

6:00.66 INFO: application_buildid: 20190425221905
6:00.66 INFO: application_changeset: d33c9556acd4b06908a89c36fbe15c2e7b6398a9
6:00.66 INFO: application_name: Thunderbird
6:00.66 INFO: application_repository: https://hg.mozilla.org/comm-central
6:00.66 INFO: application_version: 68.0a1
Was this inbound build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', 'back' or 'exit' and press Enter): good
6:15.74 INFO: Narrowed inbound regression window from [e16767ae, 87de40d0] (4 builds) to [d33c9556, 87de40d0] (2 builds) (~1 steps left)
6:15.74 INFO: No more inbound revisions, bisection finished.
6:15.74 INFO: Last good revision: d33c9556acd4b06908a89c36fbe15c2e7b6398a9
6:15.74 INFO: First bad revision: 87de40d001ca77e92342b9f1e6b5fc1f98fc4c45
6:15.74 INFO: Pushlog:
https://hg.mozilla.org/comm-central/pushloghtml?fromchange=d33c9556acd4b06908a89c36fbe15c2e7b6398a9&tochange=87de40d001ca77e92342b9f1e6b5fc1f98fc4c45

Comment 1

[Jorg K (CEST = GMT+2)]

Boy, we have no effective triaging system, so stuff like this falls through the cracks. Not even with the keyword "regression" it got picked up :-( - Magnus, take note!!

Fortunately this got reported in bug 1565840 and fixed.

Comment 2

[Jorg K (CEST = GMT+2)]

Yes, it was caused by bug 1536935.