Mozilla Firefox Browser Stable Version Releases

The last two releases have not been loading for me. After install I receive something like "Gad, we can't open the tab" I then try to open any bookmark with zero results. I doubt others have seen this as no one has complained. Any ideas?

 

Hello @Rainwalker:

Using Mozilla's own official repository, would you be able to successfully download, verify the file's signed/countersigned integrity, and install with perfect results?

Code:

https[:]//ftp.mozilla.org/pub/firefox/releases/137.0.1/

HTH

 

The update bug I've been reporting still has not been resolved.

 

Thanks 1PW, but it made no difference. Part of the error message said FF was not able to open tab.I did not have open previous windows and tabs checked in settings.

 

Hello @Rainwalker:

Have you been able to find a workaround meanwhile?

Thank you.

 

Hello @Krusty:

Have you tried the Firefox Support folks yet?

 

Hi 1PW,

This is the only article about updating to the new version, but that's what I've been doing.

As @Brummelchen posted earlier, the bug has been reported and was supposed to be fixed with FF 137.

#5642

He did give me an about:config change, which I haven't made as yet.

#5660

Thanks,
Dave

 

@Krusty, @Rainwalker, have you guys tried the Refresh Firefox option? I am guessing there might be something in your profiles or some settings you may have changed that is causing the issues for you. Please backup everything before attempting the refresh.

 

Hi @Raza0007 ,

No, not as yet, mainly in my case because it is affecting two Win10 machines, plus other people's machines as can be seen in @Brummelchen 's post linked above.

Cheers.

 

@Krusty, the strange thing is that I am not affected by that issue, so there must be something different in our profiles or settings that is causing that particular update issue for you, but not for me.

 

Hello @Krusty, @Rainwalker, @Brummelchen, and @Raza0007:

Does anyone know Mozilla's seven-digit Bug number in Bugzilla?

Thank you.

 

I guess I did not understand your question. Are you asking the seven digit bug number for a particular bug? Because every bug posted on Bugzilla is assigned a unique seven digit bug number.

 

Hello @JRViejo:

I'm referring to the failure to update FF issues experienced by @Krusty and @Rainwalker.

If it's been formally reported, a Bug number has been assigned in Bugzilla, and we can monitor its status.

Thank you.

 

Hi 1PW, as @Brummelchen posted, and I linked above:

https://bugzilla.mozilla.org/show_bug.cgi?id=1944243

https://bugzilla.mozilla.org/show_bug.cgi?id=1941931#a5216268_24572

I hope that helps.

 

The only thing that Fx137 did differently for me (on two W11 24H2 machines) was immediately after updating, browser would not restart as required, when clicking on the Restart button. This has always been standard operating procedure for me after updating Fx. After a few attempts with no restart, I closed the browser window, and then reopened. Only then was the update complete. Mainly what I'm saying is that most everything behaved somewhat normally.

 

Hello @Page42:

I experienced that failure to update after restart several times. I finally restarted my macOS Sequoia 15.4 based MBP laptop platform and forced a reinstall of FF 137.0.1 before the issue did not reappear. So I was not the only one…

HTH

 

From the Release Notes:

If this is the update bug I've been seeing, I still had to close FF to update. Will see if it's fixed next version / update.

 

Same here.

 

+1.