Strange bug

General discussion about the NoScript extension for Firefox
Post Reply
tingo
Posts: 2
Joined: Sat Dec 23, 2017 2:51 pm

Strange bug

Post by tingo » Sat Dec 23, 2017 3:09 pm

I've used NoScript for years, never changed anything to it, especially when I shut down yesterday. Neither have I changed anything in Firefox. Yet, when launching it this morning, all the sites whitelisted for years had been reset. After some amount of searching on the net, I found that this information was stored in the Profiles/~/prefs.js file. Replacing it with yesterday's backup brought the accumulated NoScript settings back again.

Can anyone tell me what happened, and what can be done to prevent it in the future? Thanks.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:45.0) Gecko/20100101 Firefox/45.0

User avatar
Giorgio Maone
Site Admin
Posts: 8715
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Strange bug

Post by Giorgio Maone » Sat Dec 23, 2017 3:27 pm

From time to time (very rarely, hopefully) the prefs.js file might get corrupted if something goes wrong while it gets written on the disk.
A good reason for making periodic backups of your profile directory.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

tingo
Posts: 2
Joined: Sat Dec 23, 2017 2:51 pm

Re: Strange bug

Post by tingo » Sat Dec 23, 2017 3:43 pm

Grazie, Giorgio. Yes, I backup my whole library at least once a day, and yes, hopefully, this kind of occurrence will remain a rare one. But it took me quite a stressful while to figure out where NoScript's information was stored. For other users, maybe this should be highlighted somewhere, somehow?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:45.0) Gecko/20100101 Firefox/45.0

User avatar
Giorgio Maone
Site Admin
Posts: 8715
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Strange bug

Post by Giorgio Maone » Sat Dec 23, 2017 3:59 pm

tingo wrote:Grazie, Giorgio. Yes, I backup my whole library at least once a day, and yes, hopefully, this kind of occurrence will remain a rare one. But it took me quite a stressful while to figure out where NoScript's information was stored. For other users, maybe this should be highlighted somewhere, somehow?
All user preferences, both for the browser and for its add-ons, are stored in prefs.js up until Firefox 57.
From then on, WebExtensions use a completely different storage layer.
So the problem, when it (rarely) happens, is much wider than "NoScript's whitelist got reset", and it's gonna affect fewer and fewer people as time passes.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Post Reply