Closed Bug 1414956 Opened 7 years ago Closed 7 years ago

nsIPrefBranch.getBoolPref failing as of 2017-11-05 nightly build

Categories

(Thunderbird :: Preferences, defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1414398

People

(Reporter: jik, Unassigned)

Details

(Keywords: regression)

All of my addons that use nsIPrefBranch.getBoolPref are failing list this starting in the 2017-11-05 nightly Linux build:

Caught Exception NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]
observe@chrome://expressionsearch/content/es.js:106:30
initPerf/<@chrome://expressionsearch/content/es.js:81:9
initPerf@chrome://expressionsearch/content/es.js:78:7
init@chrome://expressionsearch/content/es.js:28:9
@chrome://expressionsearch/content/es.js:774:1
JS frame :: chrome://expressionsearch/content/es.js :: observe :: line 106

There's no build from 2017-11-04 for me to test. The 2017-11-03 build does not have this problem.
Maybe as an add-on author of a heavy-weight add-on you should follow development in Thunderbird a little more closely to know what's going on in Daily and the problems we're having to keep up with M-C changes, particularly in the add-on area. Perhaps subscribe to maildev@lists.thunderbird.net.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Maybe if I had known about that mailing list I would have subscribed to it.

Or maybe not, since maybe the Thunderbird application maintainers should have, by now, figured out a way to effectively communicate important information about upcoming changes to add-on maintainers without making them wade through tons of discussion about how those changes are going to happen that is not useful to them.

In other words, I resort to running daily and complaining about the issues my add-ons encounter because there is no other good way for me to get the information I need about maintaining my add-ons without being inundated with information that is not useful to me.
You need to log in before you can comment on or make changes to this bug.