Hello Kevin, On Sun, 2025-05-11 at 17:48 -0700, Ken Cunningham wrote: > Some feedback for others who might try this... > > I started off by upgrading to firefox 138, which is the current default > when you install or upgrade firefox, on my DualG5 with 3.5G Ram. > > It opened, but there was no content in the windows, and none of the > firefox menus would respond after a long time.
Did you check on the CPU activity? > I uninstalled it, purged it, and reinstalled it, and same outcome. > > So I purged that, and installed the recently-fixed version of firefox 133 > from the latest snapshot. > > That opened, and then when I clicked on the interface anywhere (menus, etc) > the system hard crashed and needed to be power cycled. That happened twice > further, after rebooting each time.. > > Then I rebooted and launched X with MATE instead of my usual LXDE, for no > particular reason. Whether that had anything to do with anything, firefox > 133 then opened, and so far is working (albeit slowly) without crashing or > bringing down the system. > > I'll leave it like this for a while, and then eventually will try firefox 138 > again. I don't have any explanation for the above observations as yet, just > observations. > > As far as I can tell, all the other applications I have installed (cherrytree, > many others) are working normally. Can you run Firefox from the command line and observe the output? FWIW, I tested it remotely and it worked for me. I ran it on a ppc64 machine with the X output forwarded to my local machine and Firefox worked normally, I could browse the web without any problems. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
