No response when so many later questions were tackled.

Looks like either my question is seen as stupid or else no one can crack the freeze in Firefox.

Seems like the habit of browsing with Foxy for all these 20+ years is coming to an embarrassing end.

Old Foxy no longer has the legs to keep up with me.

Oh stop it.  ;-))

Can we get neofetch info?

What Desktop? X11 or Wayland?

I'm running just about all versions an have no issues. see screenshot

Try downloading Firefox from Mozilla. Download, unzip, and run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

Operating System: openSUSE Tumbleweed 20240801 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.2-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 125.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: HP Product Name: HP ZBook 17 G6

$ neofetch

OS: Ubuntu 22.04.4 LTS x86_64 Host: Inspiron 5567 Kernel: 6.5.0-45-generic Uptime: 2 mins Packages: 3615 (dpkg), 23 (flatpak), Shell: bash 5.1.16 Resolution: 1920x1080 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Yaru-purple [GTK2/3] Icons: Yaru-purple [GTK2/3] Terminal: gnome-terminal CPU: Intel i5-7200U (4) @ 3.100GHz GPU: Intel HD Graphics 620 GPU: AMD ATI Radeon R7 M260/M265 / M Memory: 2464MiB / 15882MiB

$ echo $XDG_SESSION_TYPE x11

I am surprised that I now seem to be back on X.org having been under the clear impression that my machine was using Wayland since 22.04 was installed. In fact I am quite sure that Wayland was originally the protocol used for graphics in 2022 and up till lately.

I suspect that when last month or two I spotted I had only Ubuntu version 22.04.2 when my server had 22.04.4 and I corrected the /etc/apt/sources.list to enable jammy-updates.

I will check the login screen to see if Wayland can be reset there using the cog-wheel.

For about 2 weeks, my Firefox Desktop v. 128.0.3 (Mozilla-Flatpak - 1.0) freezes within 30 mins of use. There is no good waiting, nothing responds except the exit button. There's a flaw in a recent update. I'm on Ubuntu 22.04.4 LTS and my Firefox is from Flatpak. While writing this I got a Flatpak update for Firefox and Firefox. Locale - whatever that is. So I'll park my question till I close and reopen Firefox - hopefully with a release from the big freeze-up.

Try your OS on live usb stick or a different desktop to see if you still have the same issue.

Not possible to try on another desktop.

While trying to restore Wayland as the gdm protocol but on reboot it stalled in Plymouth.

It's starting to look like 22.04 wasn't able to carry Wayland so a later update disabled it.

My attempts to switch back to Wayland had only made my system inoperable (boot seizes half-way through startup process with screen cursor ticking forever) and I had to use reinstallation USB to fix config file changes to gdm.

The timing of my update to Ubuntu 22.04.4 is about the same as the start of this issue with Firefox.

That's all for now.

Looked at a reinstallation/recovery version of 22.04.4 and see that it is set to X11.

It seems like the long-awaited arrival of Wayland on Ubuntu has some way to go . . .

And I'll bet the core issues haven't been fully sorted on 24.04 either.