Pale Moon forum

Normally new Linux versions are released almost same, or very shortly after, as Windows new release.
But now Linux builds have 2 days delayed.

Using the tarball Linux, Help -> Check for Updates returns "no new Pale Moon versions".

What happened?
Thanks.

I would guess Travis has something more pressing at the moment. Just be patient.

We haven't heard from Travis so we're working on building the Linux versions ourselves (Tobin is jumping into that right now). I'll be signing the binaries with my PGP key this time instead of Travis so the key needed to check will be different.
If all goes well we should have these out to Linux users later today.

Linux64 isn't a problem at all.. But as you know and some try to deny.. Linux32 is dying a slow and very annoying death. The trick is getting a 32bit environment that can build the 32bit binaries. This isn't easy because no one cares about 32bit anymore except the few who do. So a lot of resources (packages, repos, info) just aren't there anymore. Normally this wouldn't be a problem BUT since we don't use the system provided GCC toolchain but specific versions that being 7.x (or at the very least 4.9) and because these are generic builds designed for widest possible use across many distributions.. They have to be built in a very specific environment.

The ultimate problem is, no one can remember how the hell to do it and following old instructions isn't even possible anymore as UXP can't be built with anything less than 4.8 (the old instructions from 2015-16 used 4.7).

I am gonna get this figured the hell out and god help anyone and anything that gets in my way!

Sounds to me like 32bit linux palemoon is dying a slow death just like the os i guess.I find it very f*****g annoying when large internet companies dictates what hardware etc we should be catering for.Once again freedom of choice is being taken away .

Shut up, Moonraker.

Moonraker wrote:
I find it very f*****g annoying when large internet companies dictates what hardware etc we should be catering for.Once again freedom of choice is being taken away

It's called the free market place. Nobody wants 32 bit computers anymore, so why should anybody make 32 bit apps?

I've just put 64 bit linux Pale Moon 28.7.0 on all of my 64 bit linux Mint 19.2 (Tina) Xfce hard drives, did a quick test and LPM 28.7.0 is working like a champ on all of my favorite sites.

Thank you Tobin and Moonchild. Both of your expertise and help is greatly appreciated.

Just updated on my puppy linux and runs just fine as usual..thank you tobin and moonchild.!

palmoon updated from 28.6.1 to 28.7 (after "check for update" from menu help) and stop working with error: on ubuntu 12.04 latest libc.so.6 is 2.15...
how to solve the problem? (maybe palemoon updater need to check operating system and libs before update)

Hi, pr0fessor.

You are aware that Ubuntu 12.04 reached the end of its supported life more than 2 years ago (end of April 2017)?
Only in case you have subscribed to the paid Canonical extended support you will still get software updates for it. No idea how regularly and what precisely. But maybe the extended support subscription would have given you a newer libc as well.

Regards,
Karl

pr0fessor wrote: ↑

2019-09-01, 07:01

Code: Select all

/usr/lib/palemoon/palemoon: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /usr/lib/palemoon/palemoon)

on ubuntu 12.04 latest libc.so.6 is 2.15...
how to solve the problem?

Easiest way to solve the problem is by upgrading glibc, which usually entails upgrading the OS. I recommend at least Ubuntu 16.04, which is the oldest LTS release.

Funny cause the Official System Requirements for Pale Moon for Linux call for GLib 2.22 or higher. But how I built the 32bit version took that back down to 2.17.

Your system seems to ship with something even older than either of those.

So, what exactly was Travis using and why to produce the 32bit build. GCC 7 is the compiler he last used but mixing with a minimum target of at least GLib 2.15? That sounds.. unwise. If he was around I'd ask him but then again.. If he was around I wouldn't need to.

You are just gonna have to bear with the rest of us in refining exactly what Pale Moon for Linux 32bit is supposed to be going forward. Do keep in mind, however, that as far as the generic builds go and the project generally we do not nor never have specifically targeted old and insecure operating systems or ancient hardware.

Linux has a bit more flexability in this matter with more modern operating system versions that can run on older than acceptable hardware or a targeted package for a specific distribution version. But the Linux binaries we produce are more generic with a focus on running across different distributions horizontally rather than moving downward to abandoned out of date systems vertically.

pr0fessor wrote: ↑

2019-09-01, 07:01

(maybe palemoon updater need to check operating system and libs before update)

That actually wouldn't work, by the way. The updater program is part of the -previous- version of the browser, not the version downloaded. It cannot know about any version requirements the new version would have unless it was already known prior to the previous release.

Hi, pr0fessor.

Isengrim wrote: ↑

2019-09-01, 10:09

I recommend at least Ubuntu 16.04, which is the oldest LTS release.

Pale Moon 28.7.0 32-bit seems to work properly on Ubuntu 16.04 32-bit, which is the base of my Linux Mint 18.1 32-bit xfce.
I am typing this from Pale Moon 28.7.0 on Linux Mint 18.1 xfce at the moment. Regards,
Karl

As far as the Linux 32bit build is concerned, I am still conducting research and no decision has been made yet going forward. So an out of band update is not yet out of the question.

I will let you know what is happening along the way

Stay tuned!

Signing key for those that don't have it:

https://pgp.key-server.io/0x40481E7B8FCF9CEC

Was it OK that the packages in my OBS repo were ready on 30 August? I just assumed your static Linux builds were done when I saw the release announcement on the home page.