This was a problem several months ago, but since then I've made my system into a multi-lib (Thanks alienbob! It went easy as pie!) and decided to try PaleMoon once more...just to give them a fair and fighting chance.

First I downloaded the x86_64 bzipped tarball, and that wouldn't work, same problems as was reported and happening some months ago.

Then on a whim I downloaded the x86 bzipped tarball and HA! PaleMoon is working just like it once did on my 14.1 Slackware!

Anyway, not sure *why* it's working, but there you have it. Anyone who ants to try it out now knows they'll at least get good results...or hopefully as I did, heh.

Thanks for the info.-

Is this where you downloaded the browser from?
https://www.palemoon.org/

I thought that this was done before as well, multilib & x86 Pale Moon worked.

I am not going to install multilib just for Pale Moon. The Pale Moon "dev" just needs to get off that inferior distro he uses and run some real Linux -aka- Slackware.

also not going multilib just for pale moon, although I do like it a lot on android tablets.

firefox on x86 is adequate for now, although not perfect (but what is?)

by dropping flash it seems FF slowly meanders in "right" directions eventually.

adequate enough for my purposes.

I agree.

Installing multilib just for Palemoon isn't worth it. What happens if/when Palemoon segfaults again for another reason? There might not be an alternative method to make it work next time.

I'm using this Flash Plugin now (on prompt mode, of course), since Adobe is updating it: http://labs.adobe.com/downloads/flashplayer.html

Compass.

What are you reasons for it not being worth it?
Too much of a hassel?

Sorry for getting back to this so slowly...

@Ztcoracat - Yes, that's where I downloaded it from.

As for the others' statements...I didn't go multilib just so I could try out PaleMoon. I went multilib long before that so I could use my printer. I hadn't even thought of PaleMoon until just the other day I saw something that reminded me of it and that's when I decided to try it out again.

One of the reasons I like PaleMoon is it uses relatively less resources than Seamonkey (my preferred browser), is faster starting up and just running while surfing the 'net, and has so far worked better on some sites that Seamonkey couldn't get quite right (unfortunately I can't be specific at the moment as I always forget to write down something like that sites URL). One drawback it does have to Seamonkey is that I can't get to my saved passwords when I need to look one up for whatever reason.

Granted, the dev does need to start using a decent Linux distro, not necessarily Slackware (though that'd surely get him to *truly and honestly* learn about Linux far better!), but anything besides that garbage *buntu crapware.

I totally agree with you, Pale Moon is far faster than FireCrap, and is a lot easier on resources. I have Pale Moon x86_64 on -current, but I have had it since before Feb 23rd and kept -current and Pale Moon updated since. I have actually been putting off installing 14.2 because Pale Moon doesn't work properly anymore on it.

It's a combination of things.

1. Palemoon developers don't care about fixing what causes the segmentation fault, even though it affects other Linux Distributions;
2. If Palemoon developers won't fix it, what happens when Palemoon segmentation faults for another reason? Will that be fixed or left alone?;
3. I have nothing against multilib. I've used it in the past, but the bug is in Palemoon. I don't think the user is meant to use workarounds for bugs;
4. I switched back to Firefox for now. At least I can use the same places.sqlite from Palemoon. If I had the necessity to use multilib for other reasons (like something that can't be postponed), sure I'd use it.

Compass.

I'm nearly done with a SlackBuild to build it from source.

Can you elaborate a little? Like what arch?
It would be much appreciated if you can get it working on x86_64.

1 members found this post helpful.

I compiled it for 64 bit, and that is what I'm running. I just need to do some final touches to my SlackBuild and then I'll submit it to SlackBuilds.org and upload it to my notabug repo.

4 members found this post helpful.

Thanks for the details.
I'm not fond of fixing bugs so I may not go with Pale Moon afterall.

I have Palemoon 26.4.1 running under current x64 without any problems, and have had other versions running under 14.1 without any problems for over 6 months.
I've used three methods to install the binary from the developer, all being varily small (29M) compared to the source (79M) and need for Mozilla tools.
The way to do this is.
1) I simply download the latest version, unpack it to /opt and followed the manual installation page of the website for making symlinks. Maybe that isn't popular, because you have to remember not to trust /var/log/packages for palemoon status, but it works without trouble.
or 2) Downloads the version from slackbuilds.org and, following the slackbuild instructions, modify the slackbuild and info files for the version to be build, then execute the slackbuild and finally installpkg the resulting SBO.tgz in /tmp.
or 3) using sbopkg, use the search function to gather the palemoon slackbuild and then edit the slackbuild and info file to the version you'd like and finally choose "Process, Build, Install".

All three methods produce usable 64bit Palemoon, because all three are working with the binary not the source. When it comes to upgrades, I'll simply edit the slackbuild and info file, build and installpkg the newest version.

I'll be interested to see what the source builds turnout to look like in size and function, but for now I'm working and writing with Palemoon 26.4.1 Enjoy.

Here is the SlackBuild I wrote for palemoon, to compile palemoon from source.

https://notabug.org/khronosschoty/Sl...aster/palemoon

I tested it in a pure untouched install of slackware64-14.2 and it appears to run flawlessly.

5 members found this post helpful.