Firefox-128 fails to start GUI on Linux Fedora fc20.x86_64
Contents: Conditions, Problem, Observations, Motivation
Conditions
System: Linux Fedora fc20.x86_64, CPU i520M, 3.66 GiB RAM on DELL E5410
Libraries have been updated from rpm packages of Fedora distribution fc21.x86_64 to satisfy the requirements for Firefox 128 and now following versions of relevant libraries and packages are installed:
X.Org 1.14.4, libstdc++ 4.8.3, glibc 2.18, libglib 2.42.1, GTK+ 3.14.5
NetworkManager-0.9.9.0, dbus-1.6.30, GNOME 3.10.0, PulseAudio 5.0
Updating to newer version of Fedora is not possible option for me now.
Firefox 128.0.3 tarball has been unpacked to /usr/local/lib64/firefox128
Executable bash script, /usr/local/bin/firefox128 has been used to launch Firefox 128, it contains two lines
export LD_LIBRARY_PATH=/usr/local/lib64/firefox128:$LD_LIBRARY_PATH /usr/local/lib64/firefox128/firefox $1
Existing file $HOME/.mozilla has been temporarily renamed to avoid hardly possible conflicts while testing the new version of Firefox. (Later I have found that this is not necessary because new installs
of Firefox do not conflict with the previous).
Problem
Execution of the bash script, firefox128 from gnome-terminal command line started Firefox 128 but without GUI. Only the small white interval at left upper corner of the desktop appeared and it could be extended by using mouse to empty (white) window created by Gnome and titled, Firefox.
Observations
After Firefox 128.0.3 started the output of the command, ps -flu username revealed,
/usr/local/lib64/firefox128/firefox
/usr/local/lib64/firefox128/firefox-bin \
-contentproc -parentBuildID 20240725162350 \
-prefsLen 21615 -prefMapSize 245327 \
-appDir /usr/local/lib64/firefox128/browser \
{d54171b1-8a79-44b3-a271-db4e09db2365} 3715 true socket
Two parameters preceding `true socket` vary from launch to launch.
Executions of, firefox128 --help
firefox128 --full-version
display the expected output
In the way of successive approximations to highest Firefox version that starts with GUI in my system I have found this is Firefox 95.0.2
The binaries firefox in Firefox versions from 96.0 to 99.0.1 do not launch firefox-bin and the application hangs requiring explicit kill
Firefox versions 100.0.2, 101.0, 106.0, 106.0.5, 117.0, 117.0.1, 123.0.1, 128.0 I have tested like Firefox 128.0.3 behave in the same way as Firefox 128.0.3 with the same effects.
Output of the command, ps -flu username obtained when Firefox 95.0.2 is running with GUI in my system differs specifically from outputs of this command for Firefox versions above 100 Last argument for firefox-bin in those Firefox versions i.e. 100.0.2 and newer is `socket` whereas in Firefox 95.0.2 the last argument is `tab` as in the case,
/usr/local/lib64/firefox95/firefox-bin \
-contentproc -childID 2 -isForBrowser \
-prefsLen 4814 -prefMapSize 241644 -jsInitLen 278884 \
-parentBuildID 20211218203254 \
-appDir /usr/local/lib64/firefox95/browser 9563 true tab
/usr/local/lib64/firefox95/firefox-bin \
-contentproc -childID 6 -isForBrowser \
-prefsLen 5627 -prefMapSize 241644 -jsInitLen 278884 \
-parentBuildID 20211218203254 \
-appDir /usr/local/lib64/firefox95/browser 9563 true tab
/usr/local/lib64/firefox95/firefox-bin \
-contentproc -childID 7 -isForBrowser -prefsLen 5627 \
-prefMapSize 241644 -jsInitLen 278884 \
-parentBuildID 20211218203254 \
-appDir /usr/local/lib64/firefox95/browser 9563 true tab
During executing both the bash scripts firefox128 and firefox95, launching the respective Firefox versions, Firefox writes messages to stdout (gnome-display) but the outputs do not differ qualitatively.
For firefox128 the only intriguing mesasage is the last one that appears while closing Firefox 128, [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt
These messages not differing qualitatively for Firefox 95.0.2 and Firefox 128 can be summarized as follws (firefox:5370): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed gtk_style_context_get_state: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed gtk_style_context_get_property: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed gtk_style_context_get_background_color: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed gtk_style_context_get_color: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(firefox:5370): GLib-GObject-CRITICAL **: \ g_value_unset: assertion 'G_IS_VALUE (value)' failed
(firefox:2901): GLib-GObject-CRITICAL **: \ g_object_ref: assertion 'object->ref_count > 0' failed and g_object_unref: assertion 'object->ref_count > 0' failed
[GFX1-]: glxtest: libEGL missing methods
For Firefox 128 they are preceded by warnings like, [Parent 4185, Main Thread] WARNING: \ g_value_unset: assertion 'G_IS_VALUE (value)' failed: \ 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:187
Moreover during starting Firefox in versions 96.0 - 117.0.1
there is the message,
os_mmap failed.: Cannot allocate memory
This message is absent either in Firefox 95.0.2 and Firefox 128.0, 128.0.3
Motivation
The effect just described looks very strange but may be common to older versions of Linux distributions still being used by number of people with various motivations.
Various institutions, particularly banks, require "newest" versions of a browser and I am afraid that Firefox 95.0.2 working in my system will be very soon considered outdated that will result in lack of electronic access to bank account.
Therefore solving the problem just presented appears to be important.
Thank you in advance
All Replies (2)
To address the issue of Firefox 128.0.3 not displaying the GUI on your older Linux Fedora system, we need to consider compatibility and configuration problems. Try following these steps:
Steps to Solve the Issue Check GTK+ and GLib Compatibility: Ensure that the versions of GTK+ and GLib on your system are fully compatible with Firefox 128.0.3. You might need to upgrade these libraries or recompile Firefox with the versions you have.
Set Environment Variables: Sometimes, setting specific environment variables can help Firefox run correctly.
bash script: export MOZ_GTK_TITLEBAR_DECORATION=client export MOZ_USE_XINPUT2=1 export GDK_BACKEND=x11
Check Library Dependencies: Ensure all necessary libraries are installed and up to date. You can use the ldd command to check for missing libraries.
bash script: ldd /usr/local/lib64/firefox128/firefox-bin Install any missing libraries via your package manager.
Run Firefox in Safe Mode: Try running Firefox in Safe Mode to disable extensions and themes that might be causing issues.
bash script: /usr/local/lib64/firefox128/firefox --safe-mode Test with a Clean Profile: Create a new, clean profile to rule out configuration issues.
bash script: /usr/local/lib64/firefox128/firefox -ProfileManager Check for X.Org and GPU Driver Issues: Make sure your X.Org server and GPU drivers are correctly installed and configured. Sometimes, rendering issues can be related to these components.
Monitor System Logs: Check system logs for additional clues.
bash script: journalctl -xe Downgrade or Use ESR Version: If Firefox 128.0.3 continues to cause issues, consider using the Firefox Extended Support Release (ESR) version, which might be more stable on older systems.
Example Solution Implementation Install Missing Dependencies:
bash script:' sudo dnf install gtk3 glib2 Modify Launch Script: Update your firefox128 script to include additional environment variables:
bash script: export LD_LIBRARY_PATH=/usr/local/lib64/firefox128:$LD_LIBRARY_PATH export MOZ_GTK_TITLEBAR_DECORATION=client export MOZ_USE_XINPUT2=1 export GDK_BACKEND=x11 /usr/local/lib64/firefox128/firefox $1 Run Firefox in Safe Mode and with Clean Profile:
bash script: /usr/local/lib64/firefox128/firefox --safe-mode /usr/local/lib64/firefox128/firefox -ProfileManager
Conclusion: By following these steps, you can diagnose and potentially resolve the issue with Firefox 128.0.3 not displaying the GUI on your Fedora system. [edited out suggestion to use a outdated old Firefox version as this response was from a ai chatbot]. Regular maintenance and ensuring compatibility with your system's libraries and drivers are key to preventing such issues.
James moo ko soppali ci
Thank you for your answer, I have followed your suggestions: The only change resulting from export of the additional environment variables you have named is that the empty window created by Gnome has become transparent ie. without the white background.
Providing arguments --safe-mode or -ProfileManager results in lack of the empty window created by Gnome.
I had done other checks concerning libraries you have mentioned yet before asking for help.
Therefore I will continue using Firefox 95.0.2 now and I am waiting for a new version that maybe will work on my system.
Regards
NoahSUMO moo ko soppali ci
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.