Page 1 of 1

Palemoon Update 33.3 Crashed palemoon(Solved)

Posted: Fri Aug 16, 2024 6:21 pm
by number77

Hello
I am running xenial64 on a Dell Latitude E6320. I was on version 32.2 of palemoon and updated as requested to 33.3. It will not open at all now.
My question is is there any way that I can downgrade back to 32.2 from the directory on ssd which I can access.
Or second question How to I uninstall and reinstall Palemoon as it quite fast and light.
My cpu is an i5 intel 3340.
Thanks
number77


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Fri Aug 16, 2024 6:43 pm
by Wiz57

I would recommend Steven Pusser's 3rd party builds, for Xenial64 maybe look at his Ubuntu offerings. If nothing there, look at the Debian ones...
I use a 32 bit Debian build of 33.1.1 on my wizzified S15Pup32, for the oldest Debian release available. Link is here:
https://software.opensuse.org/download. ... e=palemoon Grab the binary that best suits you.

As for how to uninstall your version of Palemoon depends on how it was installed! If via SFS, just "unload" the SFS using SFSLoad.
Using a DEB file, you can simply click on it in Rox, or other file manager and install it.


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Fri Aug 16, 2024 7:07 pm
by Fenyo

Hello,

As of version 33.3.0, the minimum glibc and gcc requirements for Palemoon have changed due to the newer build os (Oracle Linux 8), the 33.2.1 version, which was compiled under Centos 7, can be found here (you can still compile the newer versions under Centos 7 if you run them under older Linux), which you can "install" manually like this.


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Fri Aug 16, 2024 7:15 pm
by Wiz57
Fenyo wrote: Fri Aug 16, 2024 7:07 pm

Hello,

As of version 33.3.0, the minimum glibc and gcc requirements for Palemoon have changed due to the newer build os (Oracle Linux 8), the 33.2.1 version, which was compiled under Centos 7, can be found here (you can still compile the newer versions under Centos 7 if you run them under older Linux), which you can "install" manually like this.

Not only those changes (glibc and gcc) but also in requiring AVX for "official" builds! I may have to explore your download links Fenyo, as I've only used
Pusser's builds for the past 3 or 4 yrs.
Wiz


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Fri Aug 16, 2024 7:24 pm
by Fenyo

Not only those changes (glibc and gcc) but also in requiring AVX for "official" builds! I may have to explore your download links Fenyo, as I've only used
Pusser's builds for the past 3 or 4 yrs.
Wiz

Yes I know about the avx, but it doesn't affect Number77's processor support it, so I didn't bring it up. :D


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Fri Aug 16, 2024 7:40 pm
by mikewalsh

@number77 :-

See this post in the PaleMoon-portable thread:-

https://www.forum.puppylinux.com/viewto ... 81#p128881

A Pale Moon community member called Nuck-TH has begun compiling SSE2 builds from 33.3.0 onwards. His first builds are now available, and I've turned the first release into a Puppy-portable (with included glibc 2.28, using watchdog's 'tweak' trick).

The link for the first of these is down the bottom of that post. "Check for Updates" is still in the Menu's 'Help' section, but DON'T use it, as it will simply once again download the 'official' version which you've already discovered won't work for you. Unlike Steve Pusser, Nuck-TH hasn't yet disabled this......

@Fenyo :-

number77's Xenialpup64 will be using the standard glibc 2.23.....unlike my own highly customized version, which is running glibc 2.31, a much newer 6-series kernel and several other newer, upgraded components. This is why I've used watchdog's 'tweak' trick, which utilises an included glibc 'upgrade' to enable older Puppies to also use this newest Pale Moon.

It's a workaround which has worked well for us for several years now.

Mike. ;)


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Sat Aug 17, 2024 6:59 am
by number77

Thank you everyone for the help. Unfortunately I am getting nowhere as it seems quite complicated and I do not understand.
If it would be possible could anyone explain what I need to download and I will try that.
Thanks
number77


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Sat Aug 17, 2024 10:18 am
by mikewalsh

@number77 :-

Download the portable build available from the link in my last post above, and give it a try. See how you get on with it, and let us know if it works for you....OK?

Mike. ;)


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Sat Aug 17, 2024 1:01 pm
by bigpup

Just to confirm the Pale Moon update to 33.3.0 does work.

In BookwormPup64 it updated and is running with no issues.

But BookwormPup64, has much newer versions dependency stuff, that Pale Moon uses, than what are in Xenialpup64.


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Sat Aug 17, 2024 3:26 pm
by number77
mikewalsh wrote: Sat Aug 17, 2024 10:18 am

@number77 :-

Download the portable build available from the link in my last post above, and give it a try. See how you get on with it, and let us know if it works for you....OK?

Mike. ;)

Exactly as you said mike. 33.3 is working fine on nxenial64.
Thanks for the help.
number77


Re: Palemoon Update 33.3 Crashed palemoon(Solved)

Posted: Sat Aug 17, 2024 3:30 pm
by number77

Thanks for all the help everyone. Its working with the portable. Nice to have it working again.


Re: Palemoon Update 33.3 Crashed palemoon

Posted: Sat Aug 17, 2024 3:45 pm
by mikewalsh

@number77 :-

:thumbup: :thumbup:

@bigpup :-

bigpup wrote: Sat Aug 17, 2024 1:01 pm

Just to confirm the Pale Moon update to 33.3.0 does work.

In BookwormPup64 it updated and is running with no issues.

But BookwormPup64, has much newer versions dependency stuff, that Pale Moon uses, than what are in Xenialpup64.

TBH, that's to be expected. If you're running an AVX-capable CPU - most Intel 'Core' CPUs since about 2012 are AVX-capable; it's only 'outliers' like my Pentium that have been deliberately 'crippled' (by Intel themselves)! - and using a sufficiently new Puppy (anything from Fossapup64 onwards will be happy), the update SHOULD go smoothly for you, without any fuss.

For Fossa (and newer), the glibc and gcc stuff WILL be new enough to 'match' Moonchild/Travis's upgraded build-environment. As always, there's usually some 'workaround' or other that will still keep PM usable with a sizeable 'swathe' of older Puppies...

We're getting kinda used to this..! :lol:

Mike. ;)