Bug 24795 - Firefox extensions stopped working
Summary: Firefox extensions stopped working
Status: RESOLVED DUPLICATE of bug 24779
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-09 08:38 CEST by Dieter Schütze
Modified: 2019-05-09 13:33 CEST (History)
3 users (show)

See Also:
Source RPM: firefox-60.6.1-2.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Dieter Schütze 2019-05-09 08:38:37 CEST
Description of problem:

Addons or extensions doesnt work anymore


Steps to Reproduce:
1. update firefox with extensions (for example adblock) from previous version to firefox-60.6.1-2.mga6
2. start firefox
3. you got a message extensions doesnt work anymore

I think this has to do with the certificate expiration, but mozilla has fixed them.
So please make a new package.
Comment 1 Marja Van Waes 2019-05-09 09:53:05 CEST
This is bug #24779, which got fixed with firefox-60.6.2-1.mga6

Please update to that version and check whether it fixes the issue.

I won't close this report as duplicate before you confirm firefox-60.6.2-1.mga6 fixes the issue, because in bug #24779, comment #9, katnatek mentioned:

> Mozilla release another updates about this issue
> 
> ESR: https://www.mozilla.org/en-US/firefox/60.6.3/releasenotes/
> Regular: https://www.mozilla.org/en-US/firefox/66.0.5/releasenotes/

CC'ing tv and luigi12

CC: (none) => luigiwalser, marja11, thierry.vignaud

Comment 2 Dieter Schütze 2019-05-09 11:05:31 CEST
Ok i got the updated firefox-60.6.2-1.mga6 package with another repository.

For me, this version works.My extensions also works with master password set in Firefox. Described in https://www.mozilla.org/en-US/firefox/60.6.3/releasenotes/

For me, you can close this Bug.
Thank you for the fast response.
Comment 3 David Walser 2019-05-09 13:33:29 CEST
Dup

*** This bug has been marked as a duplicate of bug 24779 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.