14.1 != 14.2. That has been covered in this thread and the one linked to the palemoon forum. It isn't an issue with how they're installing it... There is something with the software of 14.2 that is causing an issue that didn't exist in 14.1 or prior to Feb 2016 in -current.

And if you read the thread linked earlier to the palemoon forums, you'll see that no resolution was found.

I know the two aren't the same, cheeze. However, the OP was not clear that they attempted the binary install directly as instructed by the Pale Moon developers as I read from both this thread and the originally link thread on the Pale Moon forum, from the same OP. Also the glibc Feb 2016 security patch to 2.32 was also applied to 2.17 for 14.1, so the problem is likely not the patching of glibc. The Pale Moon web pages do say that the Mozilla Build Tools are required if you are going to build locally, the SBo doesn't check if the Mozilla Build Tools are installed. Before we attempt to "build" on Slackware (any version) why not try the binary from the authors and then contact them with build error outputs for their help in properly building with the tools they recommend? Or should we continue to stumble around without following a proper diagnosis flow. If the binary installs when following the authors directions, then clearly there is an issue with the available tools (version inclusive) on the build system, which is resolved with the binary. If the binary fails to run then a required application or version of application is missing on the target system. Either failure moves this along farther than the thread is now, with questions back to the Pale Moon developers about what is missing to cause the "seg-fault".

It's been stated in here that both binary and compilations have been attempted. Plus, OP (possibly not realizing it) didn't try to build it from source. The package created by SBo just repackages the official binary.

Then, directly after your first reply, Skaendo said the following, which covers all the scenarios.

And OP here is not the same person who opened the thread on the palemoon forums (at least they aren't the same screen name). Skaendo has posted on both this thread and the one on the palemoon forums, and he has done the testing to try and help the devs figure things out (without any resolution).

I told you bamunds, that yes, I did try the binary also. No, I didn't post anything on the Palemoon forums.

This is *not* a Slackware problem. If a regular Joe has to jump through the hoops you describe and the dev's are describing on that link you gave, it's a Palemoon problem. How is this problem supposed to make people want to move to a Linux OS when it's going to be this difficult to use an app? There's far smarter people than me using Slackware that can't get Palemoon running and have the brains and capabilities to jump through the hoops than I, yet it's still not running on their systems.

No this is not just a Slackware issue. Gentoo, Ubuntu and Manjaro are also affected. Surprisingly all of those are using glibc-2.23. Yet trava (Pale Moon dev) insists on using an inferior distro that uses a patched glibc-2.19.

@FTIO I'm sorry but I didn't read from the following post that you had tried the Pale Moon manual install method
However, if you did use that method, I'd suggest sharing your output results with the Pale Moon development team, because I see on their "Pale Moon Linux Support" page https://forum.palemoon.org/viewforum...40dabe91adf3c1 that there are similar threads which are solved. For example https://forum.palemoon.org/viewtopic...40dabe91adf3c1 has a Slackware 14.2 user who has successfully built PM and is using it. The same thread suggest some build flags that you might try also.

To address your concern about this being an regular "Joe" issue... I find it commendable that you feel Slackware should be usable by the average person. Personally I think I'm average and I use Slackware with ease within the distribution's intended design functionality. While a computer can be simply looked at as a tool to do something, like my wife simply wants to browse the Internet for shopping, I prefer to know what the sub parts of the computer is doing to help her browse. I prefer Pale Moon's Goanna engine to the Gecko (soon to be Rocket) engine of Firefox. That doesn't mean that my wife's browser isn't usable and filling her needs. But the truth is that her version of Firefox works on her computer because the Firefox developers worked with the OS tools to make it work under her OS, not the other way around where the OS developer made the unofficial Firefox browser work with their platform. I hope you understand that if there is a problem with Pale Moon it will be solved quicker on the Pale Moon forum than here on the Slackware forum. Best regards

Please read that thread again. There was no resolution found.

1 members found this post helpful.

@Skaendo. I'm not sure why you keep trying to hi-jack this thread started by FTIO. If you are now, after abandoning Pale Moon in April, wanting to research your problem with the Pale Moon installation then you should be on the Pale Moon Linux support forum, using their method of diagnosis and getting help. Otherwise it is a waste of this forum's space to complain about an application you have no intent to use. I believe you may be a troll rather than truly interested in a solution.

Oh, I'm running Pale Moon......
Maybe you failed to notice this post here.

And I tried getting help on the Pale Moon forums.
Just like stated in this post here.

So who is wasting the "forum's space" here really?

Attached Thumbnails

 

1 members found this post helpful.

tested 26.3.3 on my 14.2 and it's running fine so i bump it on my branch

Is that a fresh clean install of 14.2? Or upgraded?

It is not working on a clean install of 14.2 here.

1 members found this post helpful.

sorry, you are right. it was segfault in clean 14.2, but it's working on my machine which track 14.2 since few releases back. I'm going to remove that commit for now

1 members found this post helpful.

Ponce and i tried to compare it with our working machines and it seems that in the working machines we both have NVidia graphics (i used NVidia blob driver) and that probably be the unspesified requirement. On my VM (where it segfault), i have Intel

Can the OP post his GPU specs? Intel/NVIdia/AMD?

1 members found this post helpful.

I'm not OP, but I have been trying on 2 Intel machines.
I'll have a AMD/nVidia running in a little bit (upgrading the CPU ATM) and I will test on that.

*Update*

I did a full clean 14.2 install on a AMD/nVidia PC then built Pale Moon 26.3.3 using SBo script and it's still segfaulting.

Skaendo: did you install the binary blob to get 3D rendering support?