I can confirm that the default is broken. Environment: * In my case: Linux Reproduction: * Download https://archive.mozilla.org/pub/thunderbird/releases/91.0.3/source/thunderbird-91.0.3.source.tar.xz * Build TB without any relevant mozconfig flags * Run the self-built TB * Install an addon Actual result: Error console shows: ``` 1630093503729 addons.xpi-utils WARN Add-on addon@example.com is not correctly signed. 2 1630093503729 addons.xpi-utils WARN addMetadata: Add-on addon@example.com is invalid: Error: Extension addon@example.com is not correctly signed(resource://gre/modules/addons/XPIDatabase.jsm:2839:15) JS Stack trace: addMetadata@XPIDatabase.jsm:2839:15 processFileChanges@XPIDatabase.jsm:3292:26 checkForChanges@XPIProvider.jsm:3020:55 startup@XPIProvider.jsm:2471:12 callProvider@AddonManager.jsm:230:31 _startProvider@AddonManager.jsm:590:17 startup@AddonManager.jsm:814:14 startup@AddonManager.jsm:3511:26 observe@addonManager.js:81:29 ``` Expected result: Addons install and work Importance: This affects everybody who builds from source. So, this is actually our bug, not a bug of the Linux distribution. The Linux distro just builds with the default config. The bug is that our default config is broken.
Bug 1727113 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I can confirm that the default is broken. Environment: * In my case: Linux Reproduction: * Download https://archive.mozilla.org/pub/thunderbird/releases/91.0.3/source/thunderbird-91.0.3.source.tar.xz * Build TB without any relevant mozconfig flags * Run the self-built TB * Install an addon Actual result: Error console shows: ``` 1630093503729 addons.xpi-utils WARN Add-on addon@example.com is not correctly signed. 2 1630093503729 addons.xpi-utils WARN addMetadata: Add-on addon@example.com is invalid: Error: Extension addon@example.com is not correctly signed (resource://gre/modules/addons/XPIDatabase.jsm:2839:15) JS Stack trace: addMetadata@XPIDatabase.jsm:2839:15 processFileChanges@XPIDatabase.jsm:3292:26 checkForChanges@XPIProvider.jsm:3020:55 startup@XPIProvider.jsm:2471:12 callProvider@AddonManager.jsm:230:31 _startProvider@AddonManager.jsm:590:17 startup@AddonManager.jsm:814:14 startup@AddonManager.jsm:3511:26 observe@addonManager.js:81:29 ``` Expected result: Addons install and work Importance: This affects everybody who builds from source. So, this is actually our bug, not a bug of the Linux distribution. The Linux distro just builds with the default config. The bug is that our default config is broken.