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.
A full upgrade to 60ESR for Slackware 14.2, including the tools to build from source, and 52ESR in /pasture for those who can't or don't want to upgrade - we couldn't have asked for more. Thanks, Pat!
I find this quite an exciting update, which is ironic since I don't use Firefox that often. But to see 52ESR upgraded to 60ESR is fantastic. And it works wonderfully, I find this a much better backup browser to Chromium than 52ESR. It was great to see this, I love this distribution.
A full upgrade to 60ESR for Slackware 14.2, including the tools to build from source, and 52ESR in /pasture for those who can't or don't want to upgrade - we couldn't have asked for more. Thanks, Pat!
Agreed. Thanks, Pat! Good to know 52ESR is available in /pasture if needed, but it's looking like I won't need it - I've liked this version of Firefox since I've used it elsewhere (although I found nothing wrong with 52ESR), it's working well so far, and the few add-ons I use still work.
My mind was kind of set on, "Not gonna like it...", but I updated a user system today, 14.1 -> 14.2 (32 bit), including the 153 kernel and new Firefox, and I think I may change my mind!
I'll still have to slog my way through about:config to get it to quiet down a bit, but so far it isn't "worse" (which I admit I expected), and is definitely an improvement in resource usage and responsiveness.
Regarding the localized build... I came to the same conclusion as ponce: the way it was done is no longer supported, and I didn't manage to find another way. Documentation on this subject is hard to find and often contradicting. However, Ruario's script worked fine, so I'll stick to that for the time being.
well, after a few more test I was able to build a localized version (on 32bit and 64bit, for firefox 60, 62 and 63b) in a slightly different way (the one described in the document I linked above used by mozilla devs to prepare the localized packages that they redistribute): I took the latest SlackBuild for firefox and modified it, trying to clean it a little for things that I'm pretty sure don't apply anymore (there are surely others, but it's a start).
if you want to try it, replace the one in /sources/xap/mozilla-firefox/ with this and fire up the build like
Regarding localization, for those like me having some default setting file and desperately trying to get their langpack activated, pref("intl.locale.matchOS", true); must be removed and replaced with pref("intl.locale.requested", "");
After Opera 12.17, i was switching mostly between Firefox and Seamonkey. I think seamonkey it is a bit underestimated, much better than the likes of palemoon eg, and it has a different look overall. I do not like the oversimplification and the "overminimalization" inspired by google's chrome. On the other hand, i do not want to use a ton of third party extensions just to gain some additional functionality. Having said that, i am okay with the FF upgrade and i think ff remains an excellent choice.
(for my desktop, the last few weeks, i am using vivaldi. Its newest version is a very good -and stable- one).
Regarding localization, for those like me having some default setting file and desperately trying to get their langpack activated, pref("intl.locale.matchOS", true); must be removed and replaced with pref("intl.locale.requested", "");
OK, in fact it loads user.js but doesn't actually apply it. This silly media autoplay is back here, while about:config reports media.autoplay.enabled as false. I've to click it to true then back to false to get it effective. Sigh, it seems I will have to find another default setting strategy.
(I hate this alchemical setup where even when you have finally got the obscure values you need to change from the web, you still have to ensure they will not silently stop working. Why can't we have a decent documented config file like most of the other software? )
Last edited by NonNonBa; 09-08-2018 at 11:18 AM.
Reason: typo
I spent some time today, upgraded FF and tried to get back the functionality of the 52ESR with the add-ons I was using.
Managed to get pretty much all that I needed, with the help of some alternative add-ons and some about:config tuning replicating the functions for the ones I couldn't find an alternative for.
There are still 6 add-ons left for which I have no alternative yet, but I'm still searching. The most painful lost is the add-on bar, but you can have a few add-on icons permanently displayed in a small field - upper-right corner.
Related to the interface, it comes with the touch-view activated by default and I chose the compact view instead. Performance is (way) superior compared to 52ESR, especially for displaying these adaptive-layout pages like Youtube&LinkedIn&co.
By not having an alternative I guess I'll stick with it.
For some of you more privacy&security concerned, this tutorial could be useful: https://vikingvpn.com/cybersecurity-...y-and-security
P.S. If you follow the tutorial for hardening your FF, be advised:
- don't touch the privacy.resistFingerprinting, if you set it on true FF will not start in fullscreen mode anymore. Use some canvas fingerprinting filter add-on instead
- with the uMatrix add-on you might get into some trouble displaying some pages and you'll need to disable it (maybe don't install it at all)
- the graph visualizations of the Lightbeam add-on could be also found in the Disconnect add-on as an extra feature.
- the rest of the instructions from the tutorial are OK
Last edited by abga; 09-11-2018 at 06:29 AM.
Reason: P.S.
With the change to Firefox Quantum (60.x), it cannot run Java applets. So, I have had to start using Seamonkey for java applets. I am very satisfied with this situation. Seamonkey works very well for java applets, and is perhaps an ideal browser for them. The Seamonkey toolbars have grips for hiding the toolbars, and that is very nice. Seamonkey is really a lot like Firefox 52.x, and shares a lot of code with Firefox 52.x, but does not support all of the extensions (still many though). Seamonkey has the same themes as Firefox, so you can likely make Seamonkey look like Firefox. Hopefully, Seamonkey will continue to support java applets for a long time. The KDE Konqueror web browser is another option that used to run java applets and probably still can. Browsers galore!
Tried it, then remembered why I usually run Seamonkey.
Reverted to 52.9.0
Me too. Enjoy supporting the Surveillance Economy? No thank you. If I wanted WebTV I would run windows, I choose not to invest hours trying to figure out how to disable snooping inside gobs of garbage script.
I'm not brilliant, but I'll never trust javascript, running binary code from the internet, that's how I was trained in the 90s.
I know I am yelling at clouds (literally!), and shaking my fists at the sky(net). I hope Pat still enjoys packaging, and everyone who likes WebTV keeps supporting him. It's not his fault there's nothing new that's very good or interesting to package. Have fun!
I'm not brilliant, but I'll never trust javascript, running binary code from the internet, that's how I was trained in the 90s.
I have news for you: we are 30 years later.
Believe or not, there are Frontend Technologies like AngularJS or VueJS, on which almost any modern interactive site is made, and which will not work at all without Javascript. And no, I do not talk about the Klingon NET.
At least this is on my World, I do not know how is in the beautiful forests from Northern California...
BTW, the Javascript is not binary code, but just plain text.
Last edited by Darth Vader; 09-09-2018 at 08:55 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.