Firefox "failed to read config file"

Ah thank you for this… the context is important. Right this have to be fixed.

It is about Hardware acceleration and the used renderer Mode. So its the driver for Librem5 gpu or kind of a mesa bug?

Edit: A working WebGL could be checked on https://get.webgl.org/
If you see a spinning cube.

Information about WebGL is on about:support

There The WebGL 2 Driver Renderer throw a WebGL creation failed message:

*tryNativeGL (FEATURE_FAILURE_EGL_CREATE)
*Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS)
...


WebGPU Default Adapter:
{
"navigator.gpu": null
}
1 Like

That was very straightforward, informative, and detailed. I wish communications from Purism were more like that.

1 Like

I never directly follow rewritten links due to my security practices, so any request to do so are treated as a phishing attempt, ignored, and marked as spam.

1 Like

Yes. It threw an error that said I needed to have Firefox installed… which I of course already did. I even uninstalled/reinstalled, but no joy.

The PMOS Firefox config worked great, even better than the old version of user0 Friendly Fox I had been using.

3 Likes

I was wrong with my suggestion that webgl is the cause of this configuration message. It must be a coincidence. Because i start firefox the first time from the terminal since i am getting that bug message by the firefox execution.

Is there no way to get that text box more verbose to tell me what setting it like to be reported to some administrator?

And is it the users setting or the configuration at compilation time when building the Fox? Did somebody know this?

Is someone here on standard/stable PureOS Update level without this issue using firefox?

Edit: Changing to some new Fresh User-Configuration did not work. You can toggle it by open firefox with a Terminal and add -p (? or was it -P).

$ firefox -p

1 Like

That’s correct. I already suggested that and tried that in the other topic on this problem. The problem does not associate with the profile. You seemingly get the error on any and every profile.

1 Like

I did the git installation you propose. It works fine now, although kind of slower to start. But why the menus and url bar are at the bottom of the screen and not at the top of the screen?
Is this configurable?

1 Like

The reason for moving the bar to the bottom is that it’s generally considered easier to use that way while holding the phone. Other mobile browsers on proprietary platforms also moved the URL bar to the bottom as phone screens grew to be 5 inches and larger.

It’s not configurable (you could remove a few lines as the patch for the no longer-working PureOS firefox-esr-mobile-config package did, searching in debian/patches/0001-PureOS-config.patch · pureos/byzantium · Librem5 / debs / firefox-esr-mobile-config · GitLab for bottom is a good way to get started - the patch no longer applies, as mobile-config-firefox changed over time).

There’s an open issue about making this configurable: Make moving the address bar to the bottom optional (#51) · Issues · postmarketOS / mobile-config-firefox · GitLab. I think it should also be possible to implement this as a setting in about:config (the GitHub - rafaelmardojai/firefox-gnome-theme: A GNOME👣 theme for Firefox🔥 does fun things like that). I am happy to help if you want to work on this and need help getting started, it’s just not been a priority for me. (Just keeping mobile-config-firefox in sync with the moving target Firefox has been time-consuming enough, and I have other projects, too)

4 Likes

OK, I understand then. I just thought that it was a bug. but since there is a reason for this, OK.

1 Like