Has anyone been able to get Palemoon running on Slackware current 32 bit? The provided binaries and compilations from source for various versions work on 14.1, but both prebuilt and locally-compiled binaries fail with a segmentation fault in libxul.so on current. I can sometimes get a stack trace from gdb but I don't know that it makes much sense - it starts with

#0 0xffffffff in ()
#1 0xffffffff in JS_ObjectToOuterObject(JSContext*, JSObject*) ()
at /tmp/palemoon/libxul.so
#2 0xffffffff in () at /tmp/palemoon/libxul.so
#3 0xffffffff in () at /tmp/palemoon/libxul.so
#4 0xffffffff in () at /tmp/palemoon/libxul.so
#5 0xffffffff in JS_WrapObject(JSContext*, JSObject**) () at /tmp/palemoon/libxul.so
#6 0xffffffff in () at /tmp/palemoon/libxul.so
#7 0xffffffff in () at /tmp/palemoon/libxul.so
#8 0xffffffff in () at /tmp/palemoon/libxul.so
#9 0xffffffff in () at /tmp/palemoon/libxul.so

and continues similarly .

Hi mfgordon and welcome to LQ,

This has been reported before, so you're not the only one:
http://www.linuxquestions.org/questi...ml#post5525137

We don't have a solution for that. I don't know if Skaendo reported this upstream or got any more information, unfortunately you'll have to progress that yourself with the palemoon developers and/or bugtracker, unless someone else here knows more.

Running fine here on two 64bit Atoms both on current.

Fails at the same place on this 64bit AMD box, also on current.

Confused!

I have been trying to figure this one out as well.
(Slackware64-current)

Could it have anything to do with some libraries not linking?

https://forum.palemoon.org/viewtopic.php?f=37&t=11800

Libraries are not linking on other distros as well according to that thread, Gentoo, Ubuntu, Manjaro and I reported Slackware.

Double post sorry.

But why not all slackware-currents?

This was a fairly stock box, as usual -kde and emacs, until just the other day and it ran fine, so it's not to do with Mate.

Why Atom good, everything else bad?

Edit, this is Palemoon 26.1.1 in screenshot

Attached Thumbnails

 

No idea. I actually have Pale Moon running on 64-current. By some freak occurrence it just started working one day.

It happens on a clean fresh full install for me. If I install 14.1 and upgrade to current, then Pale Moon works fine, and I'm assuming that if Slackware(64)-current has been updated regularly, Pale Moon also runs fine.

It seems to only fail on a fresh install.

This not working box was 14.1 then current

One of the two atoms was 14.1 then current

The other atom, fresh current as of early March

All are up to date, so no clues there.

Glad you got it working tho, somehow!

Yea, it's weird. I can do a clean full install of Slackware 14.1, install Pale Moon and it runs fine.

Not the same for 14.2 RC2, it segfaults every time.
Which leads me to believe that it is something to do with one of the packages that has been upgraded.

I have a identical rig to my main rig, and it's frustrating. Firefox just drags along. Granted it's somewhat older hardware, but if I set up Firefox the exact same way that I set up Pale Moon, Firefox is SOOO slow. I do frequent re-installs on it as well, just about every update to current I do a install on that rig. So it's not just one version of Firefox, it's all of them. IMO Firefox has outgrown itself. They are adding a ton of useless (to me) stuff like "pocket", "reader mode", etc. Pale Moon just blazes right past it, and I haven't seen it slow down after having it running on my main rig for over a year now, like how after a while Firefox starts slowing down.

On my Core i5 with the latest -current updates, the 64bit version runs fine.

You're pointing fingers at random stuff, cos you don't understand what's going on. That's often understandable, but rarely constructive.

Your stack traces (both of them) quite clearly show that JS_ObjectToOuterObject, which is part of /opt/palemoon/libxul.so, which is part of Palemoon, shat on the table (to use a technical term).

The bottom line is that the binaries are built by the Palemoon project. You need to post that stack trace on their forum in the Bug Reports section.

1 members found this post helpful.