Firefox 47b3 says my unsigned extension is disabled, but it isn't

RESOLVED WORKSFORME

Status

()

Toolkit
Add-ons Manager
RESOLVED WORKSFORME
2 years ago
2 years ago

People

(Reporter: darktrojan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8750743 [details]
rect21.png

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.
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)
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

2 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

2 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)
Also look in about:config and see if any of the xpinstall preferences are non-default.
(Reporter)

Comment 6

2 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
Last Resolved: 2 years ago
Flags: needinfo?(geoff)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.