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.
The changes in Firefox 68 perturbed me. Both for home use and at work where I support other users.
I don't like the upstream method of creating a new profile and setting that profile as the default. There are many discussions online about this new behavior, which started in FF 67. The idea is to support multiple profiles with multiple versions of Firefox installed. There are manual methods of restoring the original profile, but overall the default behavior is confusing for many users ("Whoa! What happened to my bookmarks!?").
I question the wisdom of this forced profile creation. I suspect a significant majority of Firefox users do not run multiple versions.
I found two ways to avoid creating a new profile when launching Firefox 68 for the first time. The first method is to hack the Firefox source code to produce a compiled binary that can create the required hash unique to each Firefox installation. That method is beyond my skills.
A second method is sneaky but effective. This method does not require generating a hash or manually using about : profile. Open a terminal window and run firefox --headless. Press Ctrl+C to terminate the instance. Then run Firefox normally from the GUI. With this approach Firefox generates the new installs.ini and amends profiles.ini without generating a new profile.
From what I can tell the hash generation code is in other-licenses/nsis/Contrib/CityHash/. I don't program in C++. I found this discussion.
Perhaps a C++ wizard can follow that discussion to provide instructions so others can create a compiled binary?
Seems the hash is reproducible within each distro/Firefox installation. For my Slackware Current VM this hash is 11457493C5A56847. I don't know if that hash is reproducible on other users' version of Current. Would other Current users please confirm? I got a different hash on a different distro but the hash is again reproducible.
The hash on my Slackware64 14.2 system is 30AA553C542FDB21. Would other Slackware64 14.2 users confirm?
A random 16 character hash can be created with cat /dev/urandom | tr -dc A-Z0-9 | head -c16. Firefox won't use that hash and seems designed only to use its own hash derived from the local Firefox install.
I don't know what would happen when a Slackware Firefox package tries to update itself from the Mozilla.com site. I don't intend to find out, either.
Firefox won't have the permission to update unless you run it as root. All the files are installed in locations that are not writeable by non-root users, so any attempts at using the built-in updater as a normal user will fail.
I haven't tried running the update as root, so I don't know what that might do, but at a minimum, it will screw up the package database.
FYI you don't need to use the archlinux's package, that's built from source on an archlinux OS...
you can download prebuilt binaries tarballs from mozilla, just like the normal edition of firefox
FYI you don't need to use the archlinux's package, that's built from source on an archlinux OS...
you can download prebuilt binaries tarballs from mozilla, just like the normal edition of firefox
Yeah, I think the updater only works when it's official builds. All the same, I don't need a useless piece of flotsam, so "ac_add_options --disable-updater" (in .mozconfig). It doesn't even try to check, or show that it's up to date, if I go to "about Firefox".
I also do ac_add_options --disable-crashreporter for good measure. Submitting crash reports for a personal build is of no use, and I can't say my firefox builds have ever crashed out of the blue, in all my years. Only once, when PGO+LTO stopped working when compiled with gcc, insta-segfault on opening. (I just use Clang and LLD now)
Yeah, I think the updater only works when it's official builds. All the same, I don't need a useless piece of flotsam, so "ac_add_options --disable-updater" (in .mozconfig). It doesn't even try to check, or show that it's up to date, if I go to "about Firefox".
Do you compile Firefox by yourself? I also want to disable this junk.
Do you compile Firefox by yourself? I also want to disable this junk.
Yes, I compile Firefox. I use my own custom .mozconfig and just send it to /opt/firefox. You can use the SlackBuild though, I just looked at it and I see it already has those options.
Yes, I compile Firefox. I use my own custom .mozconfig and just send it to /opt/firefox. You can use the SlackBuild though, I just looked at it and I see it already has those options.
The old firefox 63 in slackware64-14.2 could really use an upgrade, an official patch package. Google maps 3D "global view" refuses to work with firefox 63. I have tried newer browsers from 3rd parties (chrome, chromium, and a newer firefox), and they all work with 3D global view. Just firefox 63 does not anymore. It is too old I guess. Sad.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.