Firefox starts with all themes disabled
Categories
(Toolkit :: Add-ons Manager, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | unaffected |
| firefox75 | --- | wontfix |
| firefox76 | --- | wontfix |
| firefox77 | --- | fixed |
People
(Reporter: flod, Assigned: mixedpuppy)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
Screenshot
It happened to me a few days ago, and today to another person in MoCo:
- Firefox suddenly started after an update completely white (I normally use Dark Mode) and missing styling in the toolbar and tabs.
- In about:addons all themes were deactivated (a state it's impossible to get into from within the browser).
Selecting one the theme (Dark Theme or Default) fixed the issue. Unfortunately I didn't manage to take a screenshot or look into the Console for hints.
|
Reporter | |
Comment 1•5 years ago
|
||
Both cases happened on macOS. For me it happened after updating to Nightly 77.0a1 (20200408033650), and only happened once.
|
|
Reporter | |
Comment 2•5 years ago
|
||
I was testing a localized build, and it happened again.
Console is full of errors for all built-ins add-ons, e.g.
1587103660060 addons.xpi WARN Exception running bootstrap method update on default-theme@mozilla.org: TypeError: can't access property "origins", oldPermissions is null(resource://gre/modules/Extension.jsm:720:7) JS Stack trace: intersectPermissions@Extension.jsm:720:7
migratePermissions@Extension.jsm:748:34
update@Extension.jsm:1666:25
callBootstrapMethod@XPIProvider.jsm:1795:33
_install@XPIProvider.jsm:1970:18
update@XPIProvider.jsm:2078:17
async*applyStartupChange@XPIDatabase.jsm:3379:67
processFileChanges@XPIDatabase.jsm:3279:14
checkForChanges@XPIProvider.jsm:2955:55
startup@XPIProvider.jsm:2415:12
callProvider@AddonManager.jsm:212:31
_startProvider@AddonManager.jsm:584:17
startup@AddonManager.jsm:808:14
startup@AddonManager.jsm:3479:26
observe@addonManager.js:87:29
Even restarting the browser doesn't solve the problem, although the console doesn't show any of these warnings anymore.
|
||
Comment 4•5 years ago
|
||
I just encountered this issue after updating from 76.0a (almost a month old) to 77.0a1 (today's build).
The issue persists even after restarting the browser.
I don't see the reported warnings, which means that we need to fix up the issue by re-enabling the last known theme when we have a proper fix for bug 1628239.
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 5•5 years ago
|
||
|
||
Updated•5 years ago
|
|
|
Assignee | |
Updated•5 years ago
|
|
||
Comment 7•5 years ago
|
||
| bugherder | ||
|
||
Updated•5 years ago
|
|
|
||
Comment 8•5 years ago
|
||
This did not work for me. I just updated from Nightly 77.0a1 to Nightly 78.0a1 buildID 20200504205324 on macOS, and all themes are still disabled. Before the version bump I also updated a few times within 77.0a1 without success, and hoped that the bump to 78.0a1 would fix it. Unfortunately not.
Shane, should this bug be re-opened or should I file a new one?
Description
•