Just a FTR but I like Palemoon very much but it segfaults often for me as well. I use KDE most commonly and had the Oxygen theme but installed AlienBob's patch. Palemonn launched and would run and even open several tabs but when loading some pages would insta-crash with segfault. I took out all instances of Oxygen, not just the theme, but to no avail. I didn't install the binary (palemoon-bin) version but built the alternative full build.

I'd really like to fix Palemoon for several reasons most notably ALSA support and my suspicion that Firfox is doing a lot more tracking than I am comfortable with. I'm seeing little popup message balloons that are totally new to me and only from a Firefox Nightly build and have yet to discover the exact source to turn it off. I'd hate to wave bye-bye to Firefox but I hate losing complete control even more. SeaMonkey works OK but it is not as snappy or as comfortable as Palemoon for me. I'm keeping watch here to see what develops on this segfault-KDE issue.

1 members found this post helpful.

If you compiled it your self, did you use gcc 4.9.4 or what did you use to compile it? If you used the stock gcc in Slackware you can expect there to be segfaults.

Thanks khronosschoty, I did indeed use 14.2's stock gcc. I think I will wait until next full release then to rely on palemoon then. One app isn't enough motivation to me for so fundamental a change since everything else works flawlessly as is. At least now I know why it segfaults.

Version 28 is released now and I'm moments away from submitting updates to SBo it does not require gcc 4.9.4.

2 members found this post helpful.

Does it work with gcc 8.2.0?

yes it does.

2 members found this post helpful.

Picked up a copy of 28 via your link at the Pale Moon Project.
So far, very good.
Many thanks!

2 members found this post helpful.

Very nice khronosschoty !

Thank you for the palemoon.SlackBuild package !

I downloaded your palemoon.tar.gz from the PM Site and set up a build.

Just a couple things didn't work 'out of the box' but maybe I am doing it wrong.

The DOWNLOAD="..." did not work with my standard `( . palemoon.info ; for d in $DOWNLOAD ; do wget $d ; done )` but I 'found' the file on the PM site and changed palemoon.info

This is the `diff -Naur` output for your original file and the one where I changed DOWNLOAD=
The md5sums matched so I continued ...

Then there was an issue because the TarFile is called PM28.0.0_Release.tar.gz but the top-level directory in the TarFile is UXP-PM28.0.0_Release/

I worked around that with a Symlink: ln -s PM28.0.0_Release.tar.gz UXP-PM28.0.0_Release.tar.gz

I am sure there is a better way to work around where the SRCNAM= does not match the top-level directory in the TarFile but it worked for now ...

Everything in your palemoon.SlackBuild worked as expected with the SymLink and I now have palemoon-28.0.0-x86_64-1_SBo_khronosschoty.tgz

I am going to shut down palemoon-27.9.4-x86_64-1alien ; backup my ~/'.moonchild productions/pale moon' ; installpkg palemoon-28.0.0-x86_64-1_SBo_khronosschoty.tgz ; and take a joy-ride !

I'll report back in a few minutes via palemoon-28.0.0 ...

Thanks again !

-- kjh

This is the tail of my palemoon-28.0.0-x86_64-1_SBo_khronosschoty.log file:

EDIT: Posting this update from Pale Moon 28.0.0 ( /var/log/packages/palemoon-28.0.0-x86_64-1_SBo_khronosschoty )

Everything looks good. RAM usage is about the same, etc, etc, etc ...

Thanks again !

2 members found this post helpful.

There was a recent regression in git that causes the download to be broken. The link the way I have it is the standard way to download tar archives from git used by SBo and there is broken links I've heard for up to a 1000 or more SlackBuilds on SBo.

3 members found this post helpful.

In the past there were two sites I visit on a regular basis that didn't display correctly in Pale Moon and it was necessary to use a different browser just for those
two URLs. With version 28 that is no longer a problem.
@khronosschoty, thanks again.

3 members found this post helpful.

Dang !

Yes, I read about that on the slackbuild-users mailing list and didn't connect the dots ...

Thanks.

-- kjh

Many thanks to both kjhambrick and khronosschoty. I now have palemoon 28 which is still snappy and sweet and no longer have segfaults even with several tabs open and heavy media content active.

1 members found this post helpful.

All --

55020 ( aka David Spencer ; aka idlemoor ) reported on the Slackbuilds-users mailing list and here on LQ that github has fixed the broken DOWNLOAD= paths.

As khronosschoty said above, this fixes the DOWNLOAD= issue in the palemoom.SlackBuild.

The issue with the Top-Level Path Element ( UXP-PM28.0.0_Release -vs- PM28.0.0_Release ) remains however.

The SymLink I mentioned ( ln -s PM28.0.0_Release.tar.gz XUP-PM28.0.0_Release.tar.gz ) takes care of that one.

But I know there is a better way than the SymLink and maybe there is more to fix on the PM github repo ?

-- kjh

2 members found this post helpful.

The Top level domain issue should be fixed in the SlackBuild now.

2 members found this post helpful.

Downloaded and installed your latest palemoon.tar.gz

Downloaded the files in DOWNLOAD= and checked the MD5SUM= values and it worked perfectly.

This time the SRCNAM I received from github was UXP-PM28.0.0_Release.tar.gz as expected.

Ran your unmodified palemoon.SlackBuild and as expected, it worked perfectly as well.

Thanks again khronosschoty !

-- kjh

This is a variation on the downloader I posted yesterday ( called it .get-DOWNLOAD.sh )

2 members found this post helpful.