Page 1 of 1
Will this workaround break anything?
Posted: 2018-05-04, 22:34
by ron_1
The background to this question is this thread about a bug I posted
here. With the help of some members of the Mint forum, I found out a workaround. The workaround is to make the file xulstore.json found in the profile folder "read only." I've done that on Firefox ESR but not yet on Basilisk. My question is this: are there any drawbacks to making this file read only that I haven't come across yet?
Also I hope this workaround will give some clues as to how this bug can be solved.
Re: Will this workaround break anything?
Posted: 2018-05-05, 13:24
by adesh
So, there should not be any problems other than missing out any interface changes you make (unless the browser considers the file being read-only as a critical condition).
Re: Will this workaround break anything?
Posted: 2018-07-28, 22:22
by ron_1
So after all this time I made the file xulstore.json "read only" just today. Right after doing that, I noticed I was still on the older version of Decentraleyes (1.4.1). When I tried to update it with the same .xpi file I used for Pale Moon, I got a message that it wasn't compatible which perplexes me because I'm pretty sure I used the same .xpi on both browsers last time. Anyway I downloaded the version marked for FF from
here, and that one installed, but then I had both versions (1.4.1 and 1.4.2) installed. I had to manually remove version 1.4.1.
My question is, did making xulstore.json "read only" cause this issue?
Re: Will this workaround break anything?
Posted: 2018-08-02, 22:48
by ron_1
I wrote:
So after all this time I made the file xulstore.json "read only" just today. Right after doing that, I noticed I was still on the older version of Decentraleyes (1.4.1). When I tried to update it with the same .xpi file I used for Pale Moon, I got a message that it wasn't compatible which perplexes me because I'm pretty sure I used the same .xpi on both browsers last time. Anyway I downloaded the version marked for FF from here, and that one installed, but then I had both versions (1.4.1 and 1.4.2) installed. I had to manually remove version 1.4.1.
My question is, did making xulstore.json "read only" cause this issue?
I'll answer my own question. I just updated Decentrayleyes on my wife's Firefox ESR, and the same thing happened, so I guess the answer is "no." I will ask about what happened on the Decentrayleyes thread.
Re: Will this workaround break anything?
Posted: 2018-08-03, 11:34
by therube
When I tried to update it with the same .xpi file I used for Pale Moon, I got a message that it wasn't compatible
Does Basilisk use it's own UUID (GUID, whatever it might be called)?
The "PM" Decentraleyes only lists <em:id>{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}</em:id> (& 27 to 28 at that).
Re: Will this workaround break anything?
Posted: 2018-08-03, 11:37
by Moonchild
Basilisk uses the Firefox GUID
Re: Will this workaround break anything?
Posted: 2018-08-03, 11:53
by therube
Then that explains why a PM specific version (no mention of "FF") will not install in Basilisk.