Re: Firefox 133 test package for ppc64

On 12/5/25 10:48 am, 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.

I can confirm this on my system. Which is has an R7 250 in it and 
because of that lacks hardware 3d and 2d by the looks of it, so I need 
to rely on fbdev. Firefox works a lot better by not crashing on startup. 
It opens up a window but only has borders as inside content is blank. I 
also see it ignoring menus. But the menu does pop up with the right side 
widget. Once of the checkmarks turned on but the menu bar would not. It 
would not quit. I had to kill it with kill. I didn't notice any 
unusually high cpu usage when I ran top to check. From CLI it did not 
print any messages. But I could Ctrl-C it to quit.

It's way better than Epiphany, which I thought was once a humble and 
trusted browser, but one that now totally takes down my machine with a 
black screen of death. However, I got that loading by disabling GLX in 
my xorg config, but it complained that it couldn't load pages. So 
Firefox may rely GLX as well, since it's so huge, and could just as 
easily do a takedown. However, I do have another issue related to my GPU 
of choice, as my dmesg is full of GPU lock up errors. System Monitor and 
Nautilus are also faulty. From research this happens in the x86 world as 
well and no solution was found. Apart from the GPU being faulty and 
needing replacement. But, the latest Debain with xorg, is the only Linux 
install that has these issues. So xorg has some issue. Possibly another 
endianism.

I expected LXDE to be better but it may be better to test MATE by the 
looks of it. I had installed this and others. Just need to switch to it 
which isn't as easy when you can't chose on login and wrestle with apt. :-)