Closed
Bug 1196846
Opened 10 years ago
Closed 10 years ago
Some release-channel Firefox 40 profiles block unsigned addons
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1195034
People
(Reporter: vladan, Unassigned)
Details
Attachments
(3 files)
Unsigned addons are getting blocked on some of my Release Firefox 40 profiles. This blocking shouldn't happen on Release yet. David Major reproduced this issue on what looked like a new profile during a presentation, but I can't reproduce this behavior reliably.
Unsigned extensions I've seen blocked on Release so far: skype click-to-call, ted's Crash Me extension
See also some of the discussion in bug 1196078
Reporter | ||
Comment 1•10 years ago
|
||
Reporter | ||
Comment 2•10 years ago
|
||
Turns out dmajor was using Nightly after all, so ignore that data point
Updated•10 years ago
|
Attachment #8650589 -
Attachment mime type: text/x-log → text/plain
Comment 3•10 years ago
|
||
Are you able to attach the extensions.json file from the profile where you see this?
Flags: needinfo?(vdjeric)
Reporter | ||
Comment 4•10 years ago
|
||
yes, but it's at home, so I'll do it tonight
Flags: needinfo?(vdjeric)
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(vdjeric)
Reporter | ||
Comment 5•10 years ago
|
||
Flags: needinfo?(vdjeric)
Comment 6•10 years ago
|
||
Ok what you're seeing is bug 1195034. The add-on is actually disabled because it isn't compatible with your version of Firefox (it lists compatibility with 3.6 -> 21.* and it has a binary component so we obey that strictly). But because of bug 1195034 we're showing the error about it being unsigned rather than a message about it being incompatible.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•