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.
I'll see how I can get my hands on the previous 45.8.0 version (which unfortunately disappeared from all the Slackware mirrors) and install that while the Firefox devs get their act together.
George uploaded packages for 45.9.0 yesterday. As usual, this is a repackaging of official binaries with lot of locales bundled:
Sorry, but I don't have time to potty-train the new Firefox version. I'll see how I can get my hands on the previous 45.8.0 version (which unfortunately disappeared from all the Slackware mirrors) and install that while the Firefox devs get their act together.
Cheers,
Niki
I just want to make it clear I was replying to this.
Quote:
Originally Posted by SlowLearner
It would be FUN to find where exactly this is occurring or even just to eliminate where it is NOT occurring. But my debugging knowledge is pretty slim.
build firefox with debugging symbols, run it in gdb, reproduce the crash, get a backtrace and finally share it with the firefox devs.
Thanks @orbea.. I think i can do this! I know next to nothing about gdb but i'm sure i can figure it out with time. Seems like a good time waiting to happen.
@kikinovak
Quote:
Sorry, but I don't have time to potty-train the new Firefox version.
lol is ok- no need for apologies :-)
I enjoy making the time to play with inner workings and LEARN (however slowly). I'm just addicted to the learning process itself. This addiction/obsession with learning new skills and discovering how things work together is a big reason WHY i originally chose and still prefer using the slackware platform.
But yes- i do always wish i had much MORE time to play/learn or... you know, perhaps potty train troublesome glitches.
the old standard "..that's not a bug, that's a FEATURE!" lol
or my personal favorite:
There are no problems, there are only opportunities to succeed.
@Didier Spaier Thank You - Thank You !
Quote:
George uploaded packages for 45.9.0 yesterday. As usual, this is a repackaging of official binaries with lot of locales bundled:
Thanks @orbea.. I think i can do this! I know next to nothing about gdb but i'm sure i can figure it out with time. Seems like a good time waiting to happen.
To be honest, it doesn't sound very fun to do it with firefox, but if you really want to debug it that is what needs to be done. Building firefox with debugging symbols (Be sure to not strip them as many slackbuilds do by default) will probably require much more space to build than it already does... GDB will be the easy part.
Code:
gdb --args firefox 2>&1 | tee firefox.log
(in the gdb prompt)
run
(reproduce the issue now and when it crashes...)
bt
bt full
t a a f
And then you will have the entire log complete with the backtrace, a much more verbose output of the backtrace and a list all of the running threads (Which sometimes may be useful) in your new firefox.log file. You can then give this log file to a firefox developer who is interested in fixing the issue.
@orbea
Ya SEE what i mean !
I adore this community
THANKS AGAIN for the further much more detailed guidance.
Incidentally, the rob.rice on another LQ thread greatly narrowed down the cause of the abrupt seg fault mozilla firefox crashes occuring after the latest updated of:
I would suggest noscript or an equivalent addon which will disable javascript by default effectively masking this issue. At least until you enable the wrong bit of javascript on a poorly made webpage...
Here are the details from the Slackware 14.1 ChangeLog:
+--------------------------+
patches/packages/mozilla-firefox-45.9.0esr-i486-1_slack14.1.txz: Upgraded.
This release contains security fixes and improvements.
Also, switching back to the 45.x ESR branch due to instabilty of the
52.x ESR branch on Slackware 14.1.
For more information, see: https://www.mozilla.org/security/kno...irefoxESR.html
(* Security fix *)
+--------------------------+
I was having issues with; mozilla-firefox-52.0.2-x86_64-1ro as being very slow and locking. Not a ESR package but generated by latest-firefox.sh script by Ruari Oedegaard. I did a upgradepkg using ./mozilla-firefox-53.0-x86_64-1ro.tgz. Still no fun in the sun! I did some trouble-shooting and found the add-on 'IP and Domain Information' to be at fault. I simply disabled that extension and restart to find that was indeed the problem. Further checking found that add-on was replacing my DNS with a totally different address that were my preferred nameservers in '/etc/resolv.conf'. Unsure as to the locking but since disabling that add-on I have no locks using Firefox.
So to my fellow Slackers, be aware of what you are using and what are the potential issues. Check thoroughly! Even signed extensions or whatever can cause issues beyond the installed package.
Firefox 52.1.0 ESR is out. Tried to build it with my own and the standard SlackBuild which led to an error. It is a problem with FileSystemDirectoryReader.h and I think that the Mozilla developers forgot something, but I am not a C/C++ programmer. However, with this patch applied FF 52.1.0 builds fine:
Well, for Slackware stable at least maybe we could wait the end of the qualification period i.e. FF 52.2.0 ESR to switch to the 52 branch, as only then we can expect the same level of stability as for the 49 branch. Only my humble opinion, of course.
Last edited by Didier Spaier; 04-23-2017 at 10:47 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.