SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is a hack if you're using the Oxygen icon theme; just modify your launch command to point to a different theme.
It's on the forum here somewhere.
Yeah, the link is in the README for the from-source PaleMoon on SBo.
note that, in some cases, simply enabling debug might stop the crashes, so if you are willing to do some tests, might be useful to play with the parameters one at a time.
regarding the OPTIMIZE one is worth to try -Os but also simply -O (still like Alien Bob wrote above).
There is a hack if you're using the Oxygen icon theme; just modify your launch command to point to a different theme.
It's on the forum here somewhere.
In my conversations with the Pale Moon developer he mentioned that there was a commit to the oxygen-gtk2 repository which was meant to solve crashes in certain firefox-derived browsers (such as Pale Moon) but that patch was never part of an official release, so many distros do not have a proper oxygen-gtk2 package that fixes the theme-related crashes in Pale Moon.
Slackware's oxygen-gtk2 package does not contain that patch either, so I added a patched oxygen-gtk2 package to my repository at the same time when I added a palemoon package to my repository.
Alright, so I tried with ENABLE_DEBUG=yes, OPTIMIZE="-Os", and using the GTK theme override, and it still crashes reliably on http://hfboards.hockeysfuture.com/. Here is a link to the end of the terminal output and then a backtrace:
I am not bashing you, at all :-)
I think it is great that SBo has a script for a source build of Pale Moon. If possible, I always prefer programs that are compiled on Slackware instead of relying on "official binaries".
It's just that the Pale Moon developer is not a Linux guy, so he relies on some other people to tell him what's working and what not. Those people are all running some kind of Debian/Ubuntu/Mint variant, and when I told him I rely more on the stability of Slackware's un-patched compilers than on the stories about crashes on other distros, he answered that I should do what i think is best.
So, I use gcc5, and at the same time am using "-Os" as optimization flag, similar to "-O2" optimization but with better respect for code size.
What we used to have to do with Slackware's Firefox builds in the past, was to apply no optimizations at all by specifying CFLAGS="-O" and "--enable-optimization" without parameter. Perhaps I will try that in future builds of my own package.
I am at work now, so I can not test, but tonight I will test Pale Moon with Yahoo pages.
Alright, so I tried with ENABLE_DEBUG=yes, OPTIMIZE="-Os", and using the GTK theme override, and it still crashes reliably on http://hfboards.hockeysfuture.com/. Here is a link to the end of the terminal output and then a backtrace:
Alright, so I tried with ENABLE_DEBUG=yes, OPTIMIZE="-Os", and using the GTK theme override, and it still crashes reliably on http://hfboards.hockeysfuture.com/. Here is a link to the end of the terminal output and then a backtrace:
I tried accessing http://hfboards.hockeysfuture.com/ using my Pale Moon package, on Slackware64-current with Plasma 5. No issue at all. I see an ugly site with ads that span half the screen and I scrolled from top to bottom. I also clicked through on some of the links. Am I supposed to click anywhere in particular to trigger a crash?
I also visited https://www.yahoo.com/ and this site too, does not make my Pale Moon crash.
I tried accessing http://hfboards.hockeysfuture.com/ using my Pale Moon package, on Slackware64-current with Plasma 5. No issue at all. I see an ugly site with ads that span half the screen and I scrolled from top to bottom.
Oh no doubt, the ads are ugly and annoying. Hence why I normally block them.
Quote:
Originally Posted by Alien Bob
I also clicked through on some of the links. Am I supposed to click anywhere in particular to trigger a crash?
No, with my SBo build it happens within seconds of navigating to that site, whether I scroll or not. I never even got the chance to click on anything. For the record, this is with a fresh ~/.moonchild productions and no add-ons installed.
Oh no doubt, the ads are ugly and annoying. Hence why I normally block them.
No, with my SBo build it happens within seconds of navigating to that site, whether I scroll or not. I never even got the chance to click on anything. For the record, this is with a fresh ~/.moonchild productions and no add-ons installed.
I did not install particular add-ons or extensions, but Pale Moon finds the same plugins that Firefox also uses (flash player, icedtea-web, gecko mediaplayer).
Here is an update on my tests. The SBo from-source Pale Moon segfaults for me at both yahoo.com and hfboards.hockeysfuture.com. I tried with the default build options and also with ENABLE_DEBUG=yes and OPTIMIZE=-Os (together, not independently), and using the oxygen theme workaround. Using the same SlackBuild but building with gcc-4.9.4 instead of the system gcc-5.3.0, there is no segfault on either page. There is also no problem with the SBo package that repackages the official binaries, or with Alien Bob's Pale Moon package. These tests were all done on Slackware64-14.2 with multilib.
So take that for what you will. It would be nice if others could confirm my results with the SBo package built with the two different compilers.
Last edited by montagdude; 05-04-2017 at 09:45 PM.
Reason: typo
Here is an update on my tests. The SBo from-source Pale Moon segfaults for me at both yahoo.com and hfboards.hockeysfuture.com. I tried with the default build options and also with ENABLE_DEBUG=yes and OPTIMIZE=-Os (together, not independently), and using the oxygen theme workaround. Using the same SlackBuild but building with gcc-4.9.4 instead of the system gcc-5.3.0, there is no segfault on either page. There is also no problem with the SBo package that repackages the official binaries, or with Alien Bob's Pale Moon package. These tests were all done on Slackware64-14.2 with multilib.
So take that for what you will. It would be nice if others could confirm my results with the SBo package built with the two different compilers.
Thank you for reporting that. Would you mind testing aleinBob's script using the option in his build script to build palemoon with "official optimization"?
Thank you for reporting that. Would you mind testing aleinBob's script using the option in his build script to build palemoon with "official optimization"?
Hm, seems to be broken.
Code:
0:10.48 configure: error: These compiler flags are invalid: -O2 ac_add_options -msse2 ac_add_options -mfpmath=sse
0:10.48 *** Fix above errors and then restart with\
0:10.49 "/usr/bin/gmake -f client.mk build"
0:10.49 /tmp/build/tmp-palemoon/Pale-Moon-27.3.0_Release/client.mk:361: recipe for target 'configure' failed
0:10.49 gmake[2]: *** [configure] Error 1
0:10.49 /tmp/build/tmp-palemoon/Pale-Moon-27.3.0_Release/client.mk:375: recipe for target '/tmp/build/tmp-palemoon/pmbuild/Makefile' failed
0:10.49 gmake[1]: *** [/tmp/build/tmp-palemoon/pmbuild/Makefile] Error 2
0:10.49 client.mk:171: recipe for target 'build' failed
0:10.49 gmake: *** [build] Error 2
0:10.53 0 compiler warnings present.
./palemoon.SlackBuild FAILED at line 282
One more data point, since I just built it anyway. Alien Bob's Pale Moon doesn't segfault either when rebuilt here with the default optimization. The SBo version did segfault with equivalent optimization (-Os), but I also built that with ENABLE_DEBUG=yes. It's also a different version of Pale Moon. But I'm a bit burned out on compiling Pale Moon since I've done it 5-10 times in the last two days, so I'm not going to rebuild the SBo version with OPTIMIZE="-Os" and ENABLE_DEBUG=no.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.