Give it a try. If just reinstalling the mobile-config doesn’t work, give my post above a try. It worked well for me.
1 Like
OK, so when I re-install the error returns but also the interface has larger elements as before. So it must be a bug in the PureOs packaging (I guess). Maybe next update will fix it?
1 Like
Wait, do you mean that uninstalling firefox-esr, removing /usr/lib/firefox-esr folder and re-installing
solves the issue and all has normal sizes on screen?
1 Like
That’s correct.
1 Like
Nope. Unfortunately I just returned to the same situation.
Elements on firefox are tiny. If I install again firefox-esr-mobile-config then again it produces the error.
Uninstallation was
sudo apt remove firefox-esr
After that the folder /usr/lib/firefox-esr did NOT exist to remove
So I re-installed with
sudo apt install firefox-esr
1 Like
The only other things that I see from:
are
and
1 Like
The issue with the firefox-esr-mobile-config package is that it is really outdated and does not support current Firefox ESR in PureOS Byzantium. There’s an old, pending MR on Purism’s gitlab, but that MR/ the version of the mobile-config-firefox project is also outdated by now.
I just recommend you to install postmarketOS / mobile-config-firefox · GitLab instead.
If you have git installed, you can install these customizations by running:
git clone https://gitlab.postmarketos.org/postmarketOS/mobile-config-firefox.git
cd mobile-config-firefox
make
sudo make FIREFOX_DIR=/usr/lib/firefox-esr install
You can also replace the first step by downloading the lastest tar ball from https://gitlab.postmarketos.org/postmarketOS/mobile-config-firefox/-/tags, unpacking that, and then continue with step two.
5 Likes
I have loved Emma’s Mobile Friendly Firefox until the Firefox update dorked everything and the new version wouldn’t install. But I’m very happy with PostMarket config – best FF experience yet!
3 Likes
Did you try updating Friendly Fox? I updated Friendly Fox and then ran the install script.
1 Like
Thanks, postmarketOS sounds like it will be maintained well.
Will try that.
1 Like
It will not be due to the GitLab repository being archived.
1 Like
You see the true error if you open a Terminal and launch firefox from there:
[GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found.
And if you click in the Check Box…
[GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dtI have no solution right now but i do not use DRM Content on my Librem5 Firefox Browser. So i did not spent time for searching or debugging.
1 Like
No, it’s maintained and will remain maintained, please don’t claim such things without even clicking the link a few posts above.
They just moved from https://gitlab.com/postmarketOS/ (gitlab dot com) to their own gitlab instance https://gitlab.postmarketos.org/postmarketOS/ . See https://postmarketos.org/blog/2024/10/14/gitlab-migration/ for reasons why they did that.
Also, there’s hoping for Firefox to fare better on mobile without customizations, see https://nlnet.nl/project/Firefox-linuxmobile/.
(Edited links so that @FranklyFlawless can safely click them.)
2 Likes
That DRM stands for Direct Rendering Manager - Wikipedia, not Digital rights management - Wikipedia - it’s confusing, I know 
4 Likes
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