Closed
Bug 1271602
Opened 8 years ago
Closed 8 years ago
Firefox 47b3 says my unsigned extension is disabled, but it isn't
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: darktrojan, Unassigned)
Details
Attachments
(1 file)
28.18 KB,
image/png
|
Details |
Don't really have any more information than that. There's nothing unusual about this extension, it doesn't happen in a clean profile, nothing unexpected happens if I turn on AOM logging.
Comment 1•8 years ago
|
||
Dave, who can investigate this more and/or is there anything we can get from the 'broken' profile to clarify what is going on here?
Flags: needinfo?(dtownsend)
Comment 2•8 years ago
|
||
Just realized that maybe Mossop isn't available (leaving ni in case I misremembered). Andy, are there other folks who could help?
Flags: needinfo?(amckay)
Reporter | ||
Comment 3•8 years ago
|
||
The daily add-on update check just ran (I guess the first time since b3 was installed) and now the extension is disabled.
Comment 4•8 years ago
|
||
We'll look in the regular weekly add-ons manager triage, next one is tomorrow. Could you attach the add-on from your profile to the bug so we can see how its signed please?
Flags: needinfo?(geoff)
Flags: needinfo?(dtownsend)
Flags: needinfo?(amckay)
Comment 5•8 years ago
|
||
Also look in about:config and see if any of the xpinstall preferences are non-default.
Reporter | ||
Comment 6•8 years ago
|
||
This isn't worth pursuing. The problem has gone away and is unlikely to happen again. But to answer your questions, the add-on is not signed at all, and xpinstall.signatures.required is set to false.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(geoff)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•