Mozilla Firefox Browser Stable Version Releases

mozilla dont keep crash reports from about:crashes (sorry for the typo above) for ever.

according to the given link from Stupendous Man
https://support.mozilla.org/en-US/kb/crash-report

it should look like this

"bp-" means NOT submitted, others are submitted.
you need to submit otherwise there is only very little any helpful hand can do.

 

Firefox 138.0 (64-bit)

I used about:crashes, not the obvious typo

Yes I am sure I scrolled down, I scrolled the entire page. There is no "Automatically send crash reports" option.

Yes I am sure.

 

@chrisretusn,
Thanks for all clarifications.
Very odd about:crashes says "Invalid URL", and in settings there is no "Automatically send crash reports" option.
Good to know it is not because of a modification in about:config for "crash".
I have no idea what could be the cause.
The only thing I can think of is that you built Firefox using the SlackBuild that comes with the Slackware source, so you could use the release version instead of the ESR version, as you mentioned. I have no idea if that might be the cause of your issues.

 

for sure you wont any altered for "crash". the official settings modifies

Code:

browser.crashReports.unsubmittedCheck.autoSubmit2

and is false by default, like others.

but the option is complete missing. thats not normal. and i did not find any policy for it, so it cant be disabled, no way. remain a different compiled build not from mozilla. and so you answered

i dont know what you have compiled, or left out. problem behind that your build is not able to use the crash-reporter or create crashes. maybe slackware is the reason. you need to find an official build for the current stable.

 

I do not use the stock package which as you pointed out is the ESR version. I do use the same SlackBuild script to build firefox but replace the ESR tarball with the release version tarball. I don't think that this would be a reason for what I am seeing in settings.

 

I looked at

Code:

browser.crashReports.unsubmittedCheck.autoSubmit2

it is set to false.
In fact here is all the setting that start with browser.crash

 

Ha! I am pretty sure I found the crash reporter problem. The SlackBuild script contains this compile option.

Code:

--disable-crashreporter

I will remove that and recompile, takes about four hours on this computer. I will report back results.

 

Good that you found the --disable-crashreporter code.

I had no idea compiling takes so much time.
I hope the recompiled build works as expected.

 

@chrisretusn
glad you resolved it.
but have in mind that such compiler switches have reason. it could be that slackware might not compatible to this feature.

for the compiling environment. i has to be sophisticated, no ancient hardware, better: most current. enough memory, 64gig+. needed compiling environment. and some time.

 

FF still doesn't update to the latest version with the internal updater, haven't they fixed that bug?

 

Hello @3x0gR13N:

Please forgive me if I am asking the obvious, but I have not read where you mentioned it before, but have you recently verified the Enable background updates on Firefox for Windows when Firefox is not running setting?

I do not allow automatic updates and much prefer to wait a few hours before updating for the sake of safety.

HTH

 

Hi @1PW
not really related to that I think, it's just that even when manually searching for updates via the Help>About, FF just endlessly searches for updates and doesn't download anything.

 

Hello @3x0gR13N:

Of course, a Firefox → About Firefox query should go to one of Mozilla's contract CDN servers. Can the computer in question successfully: ping -c 1 aus5.mozilla.org ?

HTH

 

I have an old machine. The compile with 138.0.3 failed with the switch removed. I will have to investigate why later. Compiled with the switch succeeded. Using it now. I'm going to build a "binary" of firefox, install it and see what options I have in settings.

Well aware of these issues. I am sure there is a reason that Mr Volkerding added that build option, there are several other options that may tie in. I've got no issue with him doing this, for example the "--disable-updater" option is included, as it should be. As I mentioned to @Stupendous Man the build fails without the option, succeeds with. I haven't had a crash since my last mention of it (knock on wood).

 

I built a binary build of 138.0.3 firefox. Here is a screenshot of the applicable part in Settings.

I will stick with the source build from Slackware. This binary build trashed (changed it) my home screen. I know from past experiance it messing with Applications too. Luckily on reinstalling the source build package my home screen was back to normal. I may try troubleshooting this source build and see if I can get it to work just for the heck of it. I like challenges.

 

Yes, no problems pinging. This issue lasted for a couple of versions, at least a month or two. I remember seeing a bugreport about it but not sure if it's the same issue, hence maybe they don't know about it