Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.software.firefox > #16805 > unrolled thread

Unwanted update to 150 just happened

Back to article view | Back to alt.comp.software.firefox

Contents

  Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-25 08:45 -0700
    Re: Unwanted update to 150 just happened Retirednoguilt <HapilyRetired@fakeaddress.invalid> - 2026-04-25 13:12 -0400
      Re: Unwanted update to 150 just happened Andy Burns <usenet@andyburns.uk> - 2026-04-25 18:18 +0100
        Re: Unwanted update to 150 just happened Nobody <jock@soccer.com> - 2026-04-25 10:26 -0700
          Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-25 11:01 -0700
            Re: Unwanted update to 150 just happened Dave Royal <dave@dave123royal.com> - 2026-04-28 10:14 +0100
              Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-28 12:40 -0700
                Re: Unwanted update to 150 just happened Dave Royal <dave@dave123royal.com> - 2026-04-28 22:21 +0100
                  Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-28 19:36 -0700
                    Re: Unwanted update to 150 just happened dillinger <dillinger@invalid.not> - 2026-04-29 15:45 +0200
                      Re: Unwanted update to 150 just happened Richmond <dnomhcir@gmx.com> - 2026-04-29 15:04 +0100
                        Re: Unwanted update to 150 just happened Andy Burns <usenet@andyburns.uk> - 2026-04-29 15:10 +0100
                          Re: Unwanted update to 150 just happened Richmond <dnomhcir@gmx.com> - 2026-04-29 15:21 +0100
                            Re: Unwanted update to 150 just happened dillinger <dillinger@invalid.not> - 2026-04-29 17:26 +0200
                            Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-29 19:41 -0700
                      Re: Unwanted update to 150 just happened Richmond <dnomhcir@gmx.com> - 2026-04-29 16:47 +0100
                        Re: Unwanted update to 150 just happened Andy Burns <usenet@andyburns.uk> - 2026-04-29 16:52 +0100
                          Re: Unwanted update to 150 just happened Richmond <dnomhcir@gmx.com> - 2026-04-29 16:54 +0100
                            Re: Unwanted update to 150 just happened Andy Burns <usenet@andyburns.uk> - 2026-04-29 17:00 +0100
                              Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-02 05:41 +0000
                        Re: Unwanted update to 150 just happened dillinger <dillinger@invalid.not> - 2026-04-29 18:11 +0200
                          Re: Unwanted update to 150 just happened Dave Royal <dave@dave123royal.com> - 2026-04-29 20:20 +0100
                            Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-29 20:30 -0700
                              Re: Unwanted update to 150 just happened Richmond <dnomhcir@gmx.com> - 2026-04-30 09:10 +0100
                                Re: Unwanted update to 150 just happened Andy Burns <usenet@andyburns.uk> - 2026-04-30 10:03 +0100
                              Re: Unwanted update to 150 just happened dillinger <dillinger@invalid.not> - 2026-04-30 05:48 +0200
                                Re: Unwanted update to 150 just happened Richmond <dnomhcir@gmx.com> - 2026-04-30 14:23 +0100
                                Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-30 20:16 -0700
                                  Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-03 21:47 +0000
                                    Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-05-03 19:33 -0700
                              Re: Unwanted update to 150 just happened Dave Royal <dave@dave123royal.com> - 2026-05-01 07:04 +0000
                                Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-05-01 09:33 -0700
                                  Re: Unwanted update to 150 just happened Dave Royal <dave@dave123royal.com> - 2026-05-01 18:00 +0100
                                  Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-03 21:51 +0000
                                Re: Unwanted update to 150 just happened Dave Royal <dave@dave123royal.com> - 2026-05-03 11:52 +0000
                    Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-01 08:09 +0000
                      Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-05-01 09:17 -0700
                        Re: Unwanted update to 150 just happened Frank Miller <miller@posteo.ee> - 2026-05-01 19:10 +0200
                          Re: Unwanted update to 150 just happened R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2026-05-01 20:16 +0200
                            Re: Unwanted update to 150 just happened Nobody <jock@soccer.com> - 2026-05-01 12:57 -0700
                              Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-05-02 11:58 -0700
                                Re: Unwanted update to 150 just happened Frank Miller <miller@posteo.ee> - 2026-05-02 21:15 +0200
                                  Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-05-02 12:53 -0700
                                    Re: Unwanted update to 150 just happened Frank Miller <miller@posteo.ee> - 2026-05-02 22:25 +0200
                                      Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-05-02 22:10 -0700
                                Re: Unwanted update to 150 just happened Nobody <jock@soccer.com> - 2026-05-02 16:40 -0700
                                  Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-05-02 22:01 -0700
                                    Re: Unwanted update to 150 just happened Nobody <jock@soccer.com> - 2026-05-03 18:49 -0700
                            Re: Unwanted update to 150 just happened Frank Miller <miller@posteo.ee> - 2026-05-01 22:09 +0200
                        Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-02 12:08 +1200
                          Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-02 00:11 +0000
    Re: Unwanted update to 150 just happened R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2026-04-25 20:13 +0200
      Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-25 11:25 -0700
        Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-25 11:35 -0700
          Re: Unwanted update to 150 just happened "Alan K." <alan@invalid.com> - 2026-04-25 14:56 -0400
            Re: Unwanted update to 150 just happened -- SOLVED! The Real Bev <bashley101@gmail.com> - 2026-04-25 12:41 -0700
              Re: Unwanted update to 150 just happened -- SOLVED! "Alan K." <alan@invalid.com> - 2026-04-25 15:56 -0400
              Re: Unwanted update to 150 just happened -- SOLVED! Frank Miller <miller@posteo.ee> - 2026-04-25 23:03 +0200
                Re: Unwanted update to 150 just happened -- SOLVED! The Real Bev <bashley101@gmail.com> - 2026-04-25 14:51 -0700
                  Re: Unwanted update to 150 just happened -- SOLVED! "Alan K." <alan@invalid.com> - 2026-04-25 18:12 -0400
                    Re: Unwanted update to 150 just happened -- SOLVED! The Real Bev <bashley101@gmail.com> - 2026-04-25 22:13 -0700
            Re: Unwanted update to 150 just happened R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2026-04-26 10:12 +0200
        Re: Unwanted update to 150 just happened Frank Miller <miller@posteo.ee> - 2026-04-25 21:40 +0200
    Re: Unwanted update to 150 just happened VanguardLH <V@nguard.LH> - 2026-04-25 14:21 -0500
    Re: Unwanted update to 150 just happened -- SOLVED! The Real Bev <bashley101@gmail.com> - 2026-04-25 12:45 -0700
      Re: Unwanted update to 150 just happened -- SOLVED! The Real Bev <bashley101@gmail.com> - 2026-04-25 13:01 -0700
    Re: Unwanted update to 150 just happened micky <NONONOmisc07@fmguy.com> - 2026-04-25 19:58 -0400
      Re: Unwanted update to 150 just happened Retirednoguilt <HapilyRetired@fakeaddress.invalid> - 2026-04-26 07:42 -0400
        Re: Unwanted update to 150 just happened R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2026-04-26 18:46 +0200
          Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-26 12:11 -0700
            Re: Unwanted update to 150 just happened Nobody <jock@soccer.com> - 2026-04-26 15:47 -0700
              Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-26 17:05 -0700
                Re: Unwanted update to 150 just happened Nobody <jock@soccer.com> - 2026-04-26 18:49 -0700
                  Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-26 21:48 -0700
                    Re: Unwanted update to 150 just happened Retirednoguilt <HapilyRetired@fakeaddress.invalid> - 2026-04-27 13:42 -0400
                      Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-27 11:28 -0700
                        Re: Unwanted update to 150 just happened Retirednoguilt <HapilyRetired@fakeaddress.invalid> - 2026-04-27 16:01 -0400
                          Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-28 12:45 -0700
                        Re: Unwanted update to 150 just happened "Adam H. Kerman" <ahk@chinet.com> - 2026-04-28 00:23 +0000
                      Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-04-28 08:36 +0000
                        Re: Unwanted update to 150 just happened "Adam H. Kerman" <ahk@chinet.com> - 2026-04-28 12:35 +0000
                        Re: Unwanted update to 150 just happened Retirednoguilt <HapilyRetired@fakeaddress.invalid> - 2026-04-28 15:42 -0400
                    Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-04-28 01:14 +0000
                      Re: Unwanted update to 150 just happened "Adam H. Kerman" <ahk@chinet.com> - 2026-04-28 02:51 +0000
                        Re: Unwanted update to 150 just happened The Real Bev <bashley101@gmail.com> - 2026-04-28 12:51 -0700
                          Re: Unwanted update to 150 just happened Char Jackson <none@none.invalid> - 2026-05-08 15:06 -0500
                Re: Unwanted update to 150 just happened micky <NONONOmisc07@fmguy.com> - 2026-04-26 22:27 -0400
                Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-04-28 01:12 +0000
            Re: Unwanted update to 150 just happened Retirednoguilt <HapilyRetired@fakeaddress.invalid> - 2026-04-27 13:24 -0400
            Re: Unwanted update to 150 just happened R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2026-04-28 09:15 +0200
        Re: Unwanted update to 150 just happened Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-04-27 04:07 +0000

Page 3 of 5 — ← Prev page 1 2 [3] 4 5  Next page →

#17013

On 5/1/26 12:57, Nobody wrote:
> On Fri, 1 May 2026 20:16:24 +0200, R Daneel Olivaw
> <Danni@hyperspace.vogon.gov.invalid> wrote:
> 
>>Frank Miller wrote:
>>> The Real Bev wrote:
>>>> On 5/1/26 01:09, Lawrence D’Oliveiro wrote:
>>>>> On Tue, 28 Apr 2026 19:36:56 -0700, The Real Bev wrote:
>>>>>
>>>>>> The windows endings damaged the file such that it no longer served
>>>>>> the purpose. Fixing it worked.
>>>>>
>>>>> In case it’s relevant, I keep seeing those “^M” sequences in postings
>>>>> from you when I paste the text into Emacs.
>>>>>
>>>>> I just find that odd, for a Linux user ...
>>>>
>>>> Blame Thunderbird.
>>> 
>>> Yes. Just blame Thunderbird, blame Firefox, blame Mozilla as a whole.
>>> Or better blame Microsoft or Linux, blame the developers of software.
>>> But never take responsibility for all that weird mix up of an operating
>>> system you created but don't understand yourself.

I didn't write TB.  I'm not a programmer.

And speaking of blaming Thunderbird:  Ever since I upgraded to 139 
simetimes when I hit backspace within a quote TB adds additional CRs 
above my new text further down.  Nuisance and makes no sense at all. 
Carry on.
>>You have no idea, https://www.youtube.com/watch?v=bOR38552MJA - Blame 
>>Canada!
> 
> OT: ha, ha funny... until that disgusting epithet hurled at a
> well-known Nova Scotian singer.
Oh fine, now I had to look up the lyrics.  "And that bitch Anne Murray 
too."  As I remember, pleasant and ordinary. You were never a South Park 
fan, were you?  I would have watched it more had the dialog been easier 
to understand.
> Humour/satire doesn't carry the right to insult others by name.

Sure it does!  I think the Supremes even said so...

-- 
Cheers, Bev
   If I know that chaining yourself to a dead cow is stupid,
   how come Carly makes so much more money than I do?

[toc] | [prev] | [next] | [standalone]

#17014

The Real Bev wrote:
> On 5/1/26 12:57, Nobody wrote:
>> On Fri, 1 May 2026 20:16:24 +0200, R Daneel Olivaw
>> <Danni@hyperspace.vogon.gov.invalid> wrote:
>> 
>>>Frank Miller wrote:
>>>> The Real Bev wrote:
>>>>> On 5/1/26 01:09, Lawrence D’Oliveiro wrote:
>>>>>> On Tue, 28 Apr 2026 19:36:56 -0700, The Real Bev wrote:
>>>>>>
>>>>>>> The windows endings damaged the file such that it no longer served
>>>>>>> the purpose. Fixing it worked.
>>>>>>
>>>>>> In case it’s relevant, I keep seeing those “^M” sequences in postings
>>>>>> from you when I paste the text into Emacs.
>>>>>>
>>>>>> I just find that odd, for a Linux user ...
>>>>>
>>>>> Blame Thunderbird.
>>>> 
>>>> Yes. Just blame Thunderbird, blame Firefox, blame Mozilla as a whole.
>>>> Or better blame Microsoft or Linux, blame the developers of software.
>>>> But never take responsibility for all that weird mix up of an operating
>>>> system you created but don't understand yourself.
> 
> I didn't write TB.  I'm not a programmer.
> 
> And speaking of blaming Thunderbird:  Ever since I upgraded to 139 
> simetimes when I hit backspace within a quote TB adds additional CRs 
> above my new text further down.  Nuisance and makes no sense at all. 

So don't upgrade it. I'm using version 38.7.2 since years now without
any problems. 

[toc] | [prev] | [next] | [standalone]

#17016

On 5/2/26 12:15, Frank Miller wrote:
> The Real Bev wrote:
>> On 5/1/26 12:57, Nobody wrote:
>>> On Fri, 1 May 2026 20:16:24 +0200, R Daneel Olivaw
>>> <Danni@hyperspace.vogon.gov.invalid> wrote:
>>> 
>>>>Frank Miller wrote:
>>>>> The Real Bev wrote:
>>>>>> On 5/1/26 01:09, Lawrence D’Oliveiro wrote:
>>>>>>> On Tue, 28 Apr 2026 19:36:56 -0700, The Real Bev wrote:
>>>>>>>
>>>>>>>> The windows endings damaged the file such that it no longer served
>>>>>>>> the purpose. Fixing it worked.
>>>>>>>
>>>>>>> In case it’s relevant, I keep seeing those “^M” sequences in postings
>>>>>>> from you when I paste the text into Emacs.
>>>>>>>
>>>>>>> I just find that odd, for a Linux user ...
>>>>>>
>>>>>> Blame Thunderbird.
>>>>> 
>>>>> Yes. Just blame Thunderbird, blame Firefox, blame Mozilla as a whole.
>>>>> Or better blame Microsoft or Linux, blame the developers of software.
>>>>> But never take responsibility for all that weird mix up of an operating
>>>>> system you created but don't understand yourself.
>> 
>> I didn't write TB.  I'm not a programmer.
>> 
>> And speaking of blaming Thunderbird:  Ever since I upgraded to 139 
>> simetimes when I hit backspace within a quote TB adds additional CRs 
>> above my new text further down.  Nuisance and makes no sense at all. 
> 
> So don't upgrade it. I'm using version 38.7.2 since years now without
> any problems.

I had to upgrade it because gmail started demanding 2FA.  Bastards.

-- 
Cheers, Bev
   "Give a man a fish, and you feed him for a day.  Tell him that the
    government will give him lots of fish and he will vote for you
    forever.
    When he doesn't get any fish, blame the other guys."  -A Taxpayer

[toc] | [prev] | [next] | [standalone]

#17017

The Real Bev wrote:
> On 5/2/26 12:15, Frank Miller wrote:
>> The Real Bev wrote:
[..snip..]
>>>>>>> Blame Thunderbird.
>>>>>> 
>>>>>> Yes. Just blame Thunderbird, blame Firefox, blame Mozilla as a whole.
>>>>>> Or better blame Microsoft or Linux, blame the developers of software.
>>>>>> But never take responsibility for all that weird mix up of an operating
>>>>>> system you created but don't understand yourself.
>>> 
>>> I didn't write TB.  I'm not a programmer.
>>> 
>>> And speaking of blaming Thunderbird:  Ever since I upgraded to 139 
>>> simetimes when I hit backspace within a quote TB adds additional CRs 
>>> above my new text further down.  Nuisance and makes no sense at all. 
>> 
>> So don't upgrade it. I'm using version 38.7.2 since years now without
>> any problems.
> 
> I had to upgrade it because gmail started demanding 2FA.  Bastards.

So don't use Gmail also. I think it's a bit schizophrenic to use a Linux
system with tarballs because you want to have everything under your
exceptional control and on the other side rely on Google as your mail provider.
But you can also go on with blaming others, this time Google which you
actively selected.

[toc] | [prev] | [next] | [standalone]

#17030

On 5/2/26 13:25, Frank Miller wrote:
> The Real Bev wrote:
>> On 5/2/26 12:15, Frank Miller wrote:
>>> The Real Bev wrote:
> [..snip..]
>>>>>>>> Blame Thunderbird.
>>>>>>> 
>>>>>>> Yes. Just blame Thunderbird, blame Firefox, blame Mozilla as a whole.
>>>>>>> Or better blame Microsoft or Linux, blame the developers of software.
>>>>>>> But never take responsibility for all that weird mix up of an operating
>>>>>>> system you created but don't understand yourself.
>>>> 
>>>> I didn't write TB.  I'm not a programmer.
>>>> 
>>>> And speaking of blaming Thunderbird:  Ever since I upgraded to 139 
>>>> simetimes when I hit backspace within a quote TB adds additional CRs 
>>>> above my new text further down.  Nuisance and makes no sense at all. 
>>> 
>>> So don't upgrade it. I'm using version 38.7.2 since years now without
>>> any problems.
>> 
>> I had to upgrade it because gmail started demanding 2FA.  Bastards.
> 
> So don't use Gmail also. I think it's a bit schizophrenic to use a Linux
> system with tarballs because you want to have everything under your
> exceptional control and on the other side rely on Google as your mail provider.
> But you can also go on with blaming others, this time Google which you
> actively selected.

<sigh> I do things for myself because it's easier than letting <some 
entity> do it.  Typing cp a.txt b.txt is way simpler than hauling up two 
windows, aiming the mouse, etc.  Sometimes the easy way wins.  Using 
gmail, for instance.  I started using it when the other option was my 
ISP's server, and I didn't want to be tied into any one of those because 
I wanted to be able to switch to the cheaper one when possible. Just 
continuing is easier than configuring a new email server.

Using windows to do my taxes is easier than doing it by hand, especially 
since writing HURTS now.  Microwaving is easier than real cooking. Auto 
is easier than stick, especially if you have a broken bone. Electric is 
easier than push-mower.  Need I continue?

-- 
Cheers, Bev
    Todd Flanders' hobbies include being quiet on long rides,
    clapping to songs and diabetes.

[toc] | [prev] | [next] | [standalone]

#17025

On Sat, 2 May 2026 11:58:14 -0700, The Real Bev <bashley101@gmail.com>
wrote:

>On 5/1/26 12:57, Nobody wrote:
>> On Fri, 1 May 2026 20:16:24 +0200, R Daneel Olivaw
>> <Danni@hyperspace.vogon.gov.invalid> wrote:
>> 
>>>Frank Miller wrote:
>>>> The Real Bev wrote:
>>>>> On 5/1/26 01:09, Lawrence D’Oliveiro wrote:
>>>>>> On Tue, 28 Apr 2026 19:36:56 -0700, The Real Bev wrote:
>>>>>>
>>>>>>> The windows endings damaged the file such that it no longer served
>>>>>>> the purpose. Fixing it worked.
>>>>>>
>>>>>> In case it’s relevant, I keep seeing those “^M” sequences in postings
>>>>>> from you when I paste the text into Emacs.
>>>>>>
>>>>>> I just find that odd, for a Linux user ...
>>>>>
>>>>> Blame Thunderbird.
>>>> 
>>>> Yes. Just blame Thunderbird, blame Firefox, blame Mozilla as a whole.
>>>> Or better blame Microsoft or Linux, blame the developers of software.
>>>> But never take responsibility for all that weird mix up of an operating
>>>> system you created but don't understand yourself.
>
>I didn't write TB.  I'm not a programmer.
>
>And speaking of blaming Thunderbird:  Ever since I upgraded to 139 
>simetimes when I hit backspace within a quote TB adds additional CRs 
>above my new text further down.  Nuisance and makes no sense at all. 
>Carry on.
>>>You have no idea, https://www.youtube.com/watch?v=bOR38552MJA - Blame 
>>>Canada!
>> 
>> OT: ha, ha funny... until that disgusting epithet hurled at a
>> well-known Nova Scotian singer.
>Oh fine, now I had to look up the lyrics.  "And that bitch Anne Murray 
>too."  As I remember, pleasant and ordinary. You were never a South Park 
>fan, were you?  I would have watched it more had the dialog been easier 
>to understand.
>> Humour/satire doesn't carry the right to insult others by name.
>
>Sure it does!  I think the Supremes even said so...

Gud grief.  

Might anyone here have permission to use that epithet against the
person who submitted the msg which is the subject of this follow-up?

[toc] | [prev] | [next] | [standalone]

#17029

On 5/2/26 16:40, Nobody wrote:

>>> Humour/satire doesn't carry the right to insult others by name.
>>
>>Sure it does!  I think the Supremes even said so...
> 
> Gud grief.
> 
> Might anyone here have permission to use that epithet against the
> person who submitted the msg which is the subject of this follow-up?

Go ahead if it makes you feel better.  I know for a fact that wadded 
panties are a real bummer.

-- 
Cheers, Bev
    Todd Flanders' hobbies include being quiet on long rides,
    clapping to songs and diabetes.

[toc] | [prev] | [next] | [standalone]

#17035

On Sat, 2 May 2026 22:01:02 -0700, The Real Bev <bashley101@gmail.com>
wrote:

>On 5/2/26 16:40, Nobody wrote:
>
>>>> Humour/satire doesn't carry the right to insult others by name.
>>>
>>>Sure it does!  I think the Supremes even said so...
>> 
>> Gud grief.
>> 
>> Might anyone here have permission to use that epithet against the
>> person who submitted the msg which is the subject of this follow-up?
>
>Go ahead if it makes you feel better.  

So sad given that attitude sums up Ammurican public life, with little
regard for others.

[toc] | [prev] | [next] | [standalone]

#16999

R Daneel Olivaw wrote:
> Frank Miller wrote:
>> The Real Bev wrote:
>>> On 5/1/26 01:09, Lawrence D’Oliveiro wrote:
>>>> On Tue, 28 Apr 2026 19:36:56 -0700, The Real Bev wrote:
>>>>
>>>>> The windows endings damaged the file such that it no longer served
>>>>> the purpose. Fixing it worked.
>>>>
>>>> In case it’s relevant, I keep seeing those “^M” sequences in postings
>>>> from you when I paste the text into Emacs.
>>>>
>>>> I just find that odd, for a Linux user ...
>>>
>>> Blame Thunderbird.
>> 
>> Yes. Just blame Thunderbird, blame Firefox, blame Mozilla as a whole.
>> Or better blame Microsoft or Linux, blame the developers of software.
>> But never take responsibility for all that weird mix up of an operating
>> system you created but don't understand yourself.
>> 
> 
> You have no idea, https://www.youtube.com/watch?v=bOR38552MJA - Blame 
> Canada!

There's no need to drop undescribed youtube shit here.
Just type down what you want to say or shut up.

[toc] | [prev] | [next] | [standalone]

#17002

On Fri, 1 May 2026 09:17:43 -0700, The Real Bev wrote:

> On 5/1/26 01:09, Lawrence D’Oliveiro wrote:
>>
>> On Tue, 28 Apr 2026 19:36:56 -0700, The Real Bev wrote:
>>   
>>> The windows endings damaged the file such that it no longer served
>>> the purpose. Fixing it worked.  
>> 
>> In case it’s relevant, I keep seeing those “^M” sequences in
>> postings from you when I paste the text into Emacs.
>> 
>> I just find that odd, for a Linux user ...  
> 
> Blame Thunderbird.

Test: this reply is coming from Thunderbird.

[toc] | [prev] | [next] | [standalone]

#17003

On Sat, 2 May 2026 12:08:41 +1200, Lawrence D’Oliveiro wrote:

> Test: this reply is coming from Thunderbird.

Sorry, no, I don’t use Thunderbird, that was from Claws.

[toc] | [prev] | [next] | [standalone]

#16810

The Real Bev wrote:
> In spite of the policies.json file which has worked before. Is there a 
> new method to stop updates, or are we just hosed?
> 
> (I just made a similar post, but it doesn't seem to have taken.)
> 

I'd take a look at about:policies (under 149 or 150) and see what policy 
it suggests.  Mozilla have changed this setting's name before and it 
would not be a total shock if they changed it again.

[toc] | [prev] | [next] | [standalone]

#16811

On 4/25/26 11:13, R Daneel Olivaw wrote:
> The Real Bev wrote:
>> In spite of the policies.json file which has worked before. Is there a 
>> new method to stop updates, or are we just hosed?
>> 
>> (I just made a similar post, but it doesn't seem to have taken.)
>> 
> 
> I'd take a look at about:policies (under 149 or 150) and see what policy
> it suggests.  Mozilla have changed this setting's name before and it
> would not be a total shock if they changed it again.

149 is gone.  150 says "The Enterprise Policies service is inactive."

policies.json is listed in the Documentation List and is exactly what I 
have.

============
policies.json

{
   "policies": {
     "DisableAppUpdate": true | false
   }
}
=============

Is there perhaps a different location from firefox/distribution now?

-- 
Cheers, Bev
          Horn broken.  Watch for finger.

[toc] | [prev] | [next] | [standalone]

#16812

On 4/25/26 11:25, The Real Bev wrote:
> On 4/25/26 11:13, R Daneel Olivaw wrote:
>> The Real Bev wrote:
>>> In spite of the policies.json file which has worked before. Is there a 
>>> new method to stop updates, or are we just hosed?
>>> 
>>> (I just made a similar post, but it doesn't seem to have taken.)
>>> 
>> 
>> I'd take a look at about:policies (under 149 or 150) and see what policy
>> it suggests.  Mozilla have changed this setting's name before and it
>> would not be a total shock if they changed it again.
> 
> 149 is gone.  150 says "The Enterprise Policies service is inactive."
> 
> policies.json is listed in the Documentation List and is exactly what I
> have.
> 
> ============
> policies.json
> 
> {
>     "policies": {
>       "DisableAppUpdate": true | false
>     }
> }
> =============
> 
> Is there perhaps a different location from firefox/distribution now?


Same location/file on FF149 on a backup from March 31 :-(


-- 
Cheers, Bev
          Horn broken.  Watch for finger.

[toc] | [prev] | [next] | [standalone]

#16814

On 4/25/26 2:35 PM, The Real Bev wrote:
> On 4/25/26 11:25, The Real Bev wrote:
>> On 4/25/26 11:13, R Daneel Olivaw wrote:
>>> The Real Bev wrote:
>>>> In spite of the policies.json file which has worked before. Is there a
>>>> new method to stop updates, or are we just hosed?
>>>>
>>>> (I just made a similar post, but it doesn't seem to have taken.)
>>>>
>>>
>>> I'd take a look at about:policies (under 149 or 150) and see what policy
>>> it suggests.  Mozilla have changed this setting's name before and it
>>> would not be a total shock if they changed it again.
>>
>> 149 is gone.  150 says "The Enterprise Policies service is inactive."
>>
>> policies.json is listed in the Documentation List and is exactly what I
>> have.
>>
>> ============
>> policies.json
>>
>> {
>>      "policies": {
>>        "DisableAppUpdate": true | false
>>      }
>> }
>> =============
>>
>> Is there perhaps a different location from firefox/distribution now?
> 
> 
> Same location/file on FF149 on a backup from March 31 :-(
> 
> 
shouldn't that be just true OR false, not both?

And if you're on Linux, I don't think json works.   You do it with update manager there.

-- 
Mint 22.3,  Thunderbird 140.10.0esr,  Firefox 150.0
     Alan K.

[toc] | [prev] | [next] | [standalone]

#16818 — Re: Unwanted update to 150 just happened -- SOLVED!

On 4/25/26 11:56, Alan K. wrote:
> On 4/25/26 2:35 PM, The Real Bev wrote:
>> On 4/25/26 11:25, The Real Bev wrote:
>>> On 4/25/26 11:13, R Daneel Olivaw wrote:
>>>> The Real Bev wrote:
>>>>> In spite of the policies.json file which has worked before. Is there a
>>>>> new method to stop updates, or are we just hosed?
>>>>>
>>>>> (I just made a similar post, but it doesn't seem to have taken.)
>>>>>
>>>>
>>>> I'd take a look at about:policies (under 149 or 150) and see what policy
>>>> it suggests.  Mozilla have changed this setting's name before and it
>>>> would not be a total shock if they changed it again.
>>>
>>> 149 is gone.  150 says "The Enterprise Policies service is inactive."
>>>
>>> policies.json is listed in the Documentation List and is exactly what I
>>> have.
>>>
>>> ============
>>> policies.json
>>>
>>> {
>>>      "policies": {
>>>        "DisableAppUpdate": true | false
>>>      }
>>> }
>>> =============
>>>
>>> Is there perhaps a different location from firefox/distribution now?
>> 
>> 
>> Same location/file on FF149 on a backup from March 31 :-(
>> 
>> 
> shouldn't that be just true OR false, not both?

Yes;  That was just the listing in the documents.  Why anybody would 
choose false I have no idea.>
> And if you're on Linux, I don't think json works.   You do it with update manager there.

The update manager hasn't worked for many years.   Perplexity (my 
favored AI) finally came up with the answer.  Basically, the update 
changed the policies.json file to match the windows syntax, which 
invalidated it and allowed the update to proceed.  Perplexity's fix:

cat -A distribution/policies.json 		;reveals ^M corruption
echo '{"policies":{"DisableAppUpdate":true}}' > policies.json ;fixes it
about:policies 					;confirms "Active"

I wonder what other as-yet-undiscovered wihshit is lurking in the 
firefox/ directory.

-- 
Cheers, Bev
    All bleeding eventually stops.

[toc] | [prev] | [next] | [standalone]

#16822 — Re: Unwanted update to 150 just happened -- SOLVED!

On 4/25/26 3:41 PM, The Real Bev wrote:
> On 4/25/26 11:56, Alan K. wrote:
>> On 4/25/26 2:35 PM, The Real Bev wrote:
>>> On 4/25/26 11:25, The Real Bev wrote:
>>>> On 4/25/26 11:13, R Daneel Olivaw wrote:
>>>>> The Real Bev wrote:
>>>>>> In spite of the policies.json file which has worked before. Is there a
>>>>>> new method to stop updates, or are we just hosed?
>>>>>>
>>>>>> (I just made a similar post, but it doesn't seem to have taken.)
>>>>>>
>>>>>
>>>>> I'd take a look at about:policies (under 149 or 150) and see what policy
>>>>> it suggests.  Mozilla have changed this setting's name before and it
>>>>> would not be a total shock if they changed it again.
>>>>
>>>> 149 is gone.  150 says "The Enterprise Policies service is inactive."
>>>>
>>>> policies.json is listed in the Documentation List and is exactly what I
>>>> have.
>>>>
>>>> ============
>>>> policies.json
>>>>
>>>> {
>>>>       "policies": {
>>>>         "DisableAppUpdate": true | false
>>>>       }
>>>> }
>>>> =============
>>>>
>>>> Is there perhaps a different location from firefox/distribution now?
>>>
>>>
>>> Same location/file on FF149 on a backup from March 31 :-(
>>>
>>>
>> shouldn't that be just true OR false, not both?
> 
> Yes;  That was just the listing in the documents.  Why anybody would
> choose false I have no idea.>
>> And if you're on Linux, I don't think json works.   You do it with update manager there.
> 
> The update manager hasn't worked for many years.   Perplexity (my
> favored AI) finally came up with the answer.  Basically, the update
> changed the policies.json file to match the windows syntax, which
> invalidated it and allowed the update to proceed.  Perplexity's fix:
> 
> cat -A distribution/policies.json 		;reveals ^M corruption
> echo '{"policies":{"DisableAppUpdate":true}}' > policies.json ;fixes it
> about:policies 					;confirms "Active"
> 
> I wonder what other as-yet-undiscovered wihshit is lurking in the
> firefox/ directory.
> 
Tons of little undocumented things.  And as you make this great cheat sheet, they change 
the rules on ya.

-- 
Mint 22.3,  Thunderbird 140.10.0esr,  Firefox 150.0
     Alan K.

[toc] | [prev] | [next] | [standalone]

#16828 — Re: Unwanted update to 150 just happened -- SOLVED!

The Real Bev wrote:
[..snip..]
> The update manager hasn't worked for many years.

Which one; and which Linux distribution do you use?

> Perplexity (my 
> favored AI) finally came up with the answer.  Basically, the update 
> changed the policies.json file to match the windows syntax, which 
> invalidated it and allowed the update to proceed.  Perplexity's fix:
> 
> cat -A distribution/policies.json 		;reveals ^M corruption
> echo '{"policies":{"DisableAppUpdate":true}}' > policies.json ;fixes it
> about:policies 					;confirms "Active"

So frankly - do you understand this blabber? Do you know what it means?
Or do you blindly follow the instructions of your "favored AI"?

> I wonder what other as-yet-undiscovered wihshit is lurking in the 
> firefox/ directory.

I wonder if you are willing to understand the functions and the given
facts of a Linux system. The system that you use.

[toc] | [prev] | [next] | [standalone]

#16831 — Re: Unwanted update to 150 just happened -- SOLVED!

On 4/25/26 14:03, Frank Miller wrote:
> The Real Bev wrote:
> [..snip..]
>> The update manager hasn't worked for many years.
> 
> Which one; and which Linux distribution do you use?
> 
>> Perplexity (my 
>> favored AI) finally came up with the answer.  Basically, the update 
>> changed the policies.json file to match the windows syntax, which 
>> invalidated it and allowed the update to proceed.  Perplexity's fix:
>> 
>> cat -A distribution/policies.json 		;reveals ^M corruption
>> echo '{"policies":{"DisableAppUpdate":true}}' > policies.json ;fixes it
>> about:policies 					;confirms "Active"
> 
> So frankly - do you understand this blabber? Do you know what it means?
> Or do you blindly follow the instructions of your "favored AI"?
> 
>> I wonder what other as-yet-undiscovered wihshit is lurking in the 
>> firefox/ directory.
> 
> I wonder if you are willing to understand the functions and the given
> facts of a Linux system. The system that you use.

Sure, within limits.  Yes, I understand that.  The problem is when 
third-party entities interact with other third-party entities, doing 
things behind the scenes that are invisible to me.  I have other 
problems too, of course, but my mitochondria are of little interest to 
anyone here.

I know what cat, echo and chmod do.  So does everyone reading this 
thread, probably. Why would a linux update apply windows formatting to a 
linux file?  No idea, seems either stupid or malevolent. Why would 
anyone suspect such a thing?

I'm sorry if I upset you by posting something you felt was... uh... 
inappropriate is always a useful word.  I'll try to have a 
less-obvious-to-you problem next time.


-- 
Cheers, Bev
   "Faster, faster, until the thrill of speed overcomes the fear of death."
                                                  -- Hunter S. Thompson

[toc] | [prev] | [next] | [standalone]

#16834 — Re: Unwanted update to 150 just happened -- SOLVED!

On 4/25/26 5:51 PM, The Real Bev wrote:
> On 4/25/26 14:03, Frank Miller wrote:
>> The Real Bev wrote:
>> [..snip..]
>>> The update manager hasn't worked for many years.
>>
>> Which one; and which Linux distribution do you use?
>>
>>> Perplexity (my
>>> favored AI) finally came up with the answer.  Basically, the update
>>> changed the policies.json file to match the windows syntax, which
>>> invalidated it and allowed the update to proceed.  Perplexity's fix:
>>>
>>> cat -A distribution/policies.json 		;reveals ^M corruption
>>> echo '{"policies":{"DisableAppUpdate":true}}' > policies.json ;fixes it
>>> about:policies 					;confirms "Active"
>>
>> So frankly - do you understand this blabber? Do you know what it means?
>> Or do you blindly follow the instructions of your "favored AI"?
>>
>>> I wonder what other as-yet-undiscovered wihshit is lurking in the
>>> firefox/ directory.
>>
>> I wonder if you are willing to understand the functions and the given
>> facts of a Linux system. The system that you use.
> 
> Sure, within limits.  Yes, I understand that.  The problem is when
> third-party entities interact with other third-party entities, doing
> things behind the scenes that are invisible to me.  I have other
> problems too, of course, but my mitochondria are of little interest to
> anyone here.
> 
> I know what cat, echo and chmod do.  So does everyone reading this
> thread, probably. Why would a linux update apply windows formatting to a
> linux file?  No idea, seems either stupid or malevolent. Why would
> anyone suspect such a thing?
> 
> I'm sorry if I upset you by posting something you felt was... uh...
> inappropriate is always a useful word.  I'll try to have a
> less-obvious-to-you problem next time.
> 
> 
The ^M corruption you talk about is not corruption.   I'll get this wrong but read between 
the lines here.   Window uses carriage-return line-feed (CRLF) in text files.  Linux just 
uses carriage-return (CR).  So if you grab a policies file from you window HD, and drop it 
into Linux, it's got extra characters.  If you had opened it with a proper Linux text 
editor and saved it, you probably would have fixed it, but even that might not do it if 
the editor is not set for force Linux line endings.

The echo in Linux solves the problem nicely as it writes the file in proper Linux text 
format.

For larger files you would have to find a dos2unix script, so sed command, etc.

Xed in Mint doesn't seem to give me any issues with Windows files.

-- 
Mint 22.3,  Thunderbird 140.10.0esr,  Firefox 150.0
     Alan K.

[toc] | [prev] | [next] | [standalone]

Page 3 of 5 — ← Prev page 1 2 [3] 4 5  Next page →

Back to top | Article view | alt.comp.software.firefox

csiph-web