Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Richmond Newsgroups: alt.comp.software.firefox Subject: Re: Unwanted update to 150 just happened Date: Wed, 29 Apr 2026 16:47:12 +0100 Organization: Frantic Message-ID: <82jytp6a67.fsf@example.com> References: <10sinht$tpvi$1@dont-email.me> <10sisme$vqg1$1@dont-email.me> <10sivi0$10uuo$1@dont-email.me> <10sptp2$311i3$1@dont-email.me> <10sr2ep$3c77i$1@dont-email.me> <10sr8ck$3f3pq$1@dont-email.me> <10srqs8$3jk6e$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: solani.org; logging-data="1222677"; mail-complaints-to="abuse@news.solani.org" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:cd+GXZz7WIqpDe5FboNXk2te4Wk= sha1:zzMKnYMJG6Ncou4AjHDVPtn9IwU= X-User-ID: eJwFwYEBACAEBMCViH81jsT+I3QHo7LCCToGU5RTCntx9fprCnJh1+QxDWRwQ2dM2lZZ8wMWzxDO Xref: csiph.com alt.comp.software.firefox:16946 dillinger writes: > Op 29-04-2026 om 04:36 schreef The Real Bev: >> On 4/28/26 14:21, Dave Royal wrote: >>> The Real Bev Wrote in message: >>> >>>> On 4/28/26 02:14, Dave Royal wrote: >>>>> The Real Bev Wrote in message: >>>>> >>>>>> On 4/25/26 10:26, Nobody wrote: >>>>>>> On Sat, 25 Apr 2026 18:18:07 +0100, Andy Burns >>>>>>> wrote: >>>>>>> >>>>>>>> Retirednoguilt wrote: >>>>>>>> >>>>>>>>> I've never had FF update me autonomously. >>>>>>>> >>>>>>>> I have it set for "Check for updates but let you choose to >>>>>>>> install them" >>>>>>>> and as best as I can remember, its never disobeyed ... >>>>>>> >>>>>>> Should a user (for whatever reason) 'uninstall/re-install' then that >>>>>>> radio button changes to 'automatically install/recommended'. >>>>>>> >>>>>>> Semi-OT, Thunderbird conversely holds the 'check for updates but >>>>>>> lemme >>>>>>> do the work' setting. >>>>>> >>>>>> I have had that setting for decades -- and still do.  Some years >>>>>> ago it stopped working and some kind person posted the >>>>>> policies.json fix -- which worked until today.  Posted herewith: >>>>>> >>>>>> Make a new firefox/distribution/ subdirectory which will contain >>>>>> the file policies.json which contains >>>>>> { >>>>>>    "policies": { >>>>>>      "DisableAppUpdate": true >>>>>>    } >>>>>> } >>>>> >>>>> Did that 'kind person' provide a policies.json file for you to >>>>>   download, or did you create one - on Linux? >>>> >>>> Someone posted about that file long ago, and the one I created with >>>> pico worked for years. >>>>> Just wondering how these Windows line endings - if that was the >>>>>   problem - got there. >>>> They appeared when Firefox chose to update itself against my express >>>> wishes.  I suspect that Firefox did it of its own volition -- or >>>> simple clumsiness.  Core dump complete. >>> >>> You /found/ them after the unwanted update. Were they responsible >>>   for it? I doubt it: line endings - of either type - are ignored >>>   in a json file. >> >> The windows endings damaged the file such that it no longer served the >> purpose.  Fixing it worked. >> > > Firefox doesn't care about line endings. > > Just for the sake of it I tested it for you, I created a policies.json > which blocks about:config and tested it with both CRLF (windows) and LF > (unix) line endings. > > The result are the same for both, it works: > Blocked Page, Firefox can’t connect to the server at about:config > > ^M is not a corruption, this is how cat -A shows CR, your AI needs an > update. > > CRLF (windows): > cat -A policies.json > {^M$ > "policies": {^M$ > "BlockAboutConfig": true^M$ > }^M$ > }^M$ > > LF (unix): > cat -A policies.json > {$ > "policies": {$ > "BlockAboutConfig": true$ > }$ > }$ You tested whether it blocked about:config, but you didn't test whether it blocked an update, or if the update altered the json file.