Installing Firefox 57 - add repository or download from mozilla.org?

I found Firefox 57.0.1 here (which I suppose means I should install from “mozilla” repository, i.e. not through official repos).
I also read some threads in which people suggest to download from mozilla.org, unzip to a directory and use it this way.

Which is the recommended way and why? I also wonder - why isn’t latest stable Firefox in official openSUSE repos? It is a stable software, right?

Hi
The current Leap release is following the Firefox ESR route, it’s stable, it’s in the official oss repositories for Tumbleweed. The can’t co-exist so it’s one or the other…

My preference if I was going to run would be via a tarball download and it’s own directory just for my user…

Thanks for the quick reply.

[QUOTE=malcolmlewis;2847076]Hi
The current Leap release is following the Firefox ESR route, it’s stable, it’s in the official oss repositories for Tumbleweed. The can’t co-exist so it’s one or the other…
[/QUOTE]
I am not quite sure I understand (I also had to search what is ESR and found this). My confusion comes from the fact that I see a repo providing 57.0.1 for Leap 42.3 which is listed in the “Show unstable packages” on software.opensuse.org but at the same time it is a stable software which you also confirm. And what is it that can’t co-exist with it? I hope you can clarify.

Another thing I notice when I click “1-click install” (screenshot) - why am I asked to add 2 repos? Why is the second one needed? Is it safe? (I still haven’t confirmed anything)

My preference if I was going to run would be via a tarball download and it’s own directory just for my user…

Why is that? Because the repo can’t be trusted or something else? Is it not better to have updates via ‘zypper up’?

Sorry for so many questions.

Hi
If you press the alt key to get the menu Help -> About, then you will see it’s the ESR version, latest is only features, remember any security, important bug fixes are backported into the released versions (via updates repo).

Yes it’s the development repository, always use at your own risk, it may break your system, maybe not now…

You need to make sure you backup your ~/.mozilla folder before installing, AFAIK, they are not compatible(?) some add-ons don’t work with Quantum yet.

Quantum is built with rust (which is not in Leap), hence it needs to be added to your system for supporting libraries.

The tarball is standalone so includes supporting files all in one location, rather than system wide…

Scenario, say there is a major update to rust (since it’s a development repo) and this appears in the repository and you update, then it may break Firefox if it’s not rebuilt against the new libraries that are installed. Or a new release of quantum comes out and is not built or fails for some reason against those libraries… all just a possibility when using non-standard repositories…

Thank you so much for explaining.

Does that mean that my currently installed Firefox version (52.5.0-66.1.x86_64) already has everything which 57.0.1 has? In other words - is there any reason to update to newer version number at all?

Hi
From a security point of view, features not necessarily. Version numbers mean generally new features, or in this case a different build environment.

The question is really what can’t you do in the current release, do I need a new feature (what ever that may be)?

The openSUSE Leap model isn’t new features…

I just read that it is very fast and many other good things, so I got curious.

There’s a semi-official repo:

http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_42.3/

which seems to contain 57.0.1.

Perhaps that’s where your software search is finding it.

I currently have that repo configured but disabled. I’m inclined to stay with the ESR version, at least for a while longer.

Firefox 57 is really fast. You need not install it. Run it from the tarball.

Thanks everyone.
I will try the tarball.

Tested with http://peacekeeper.futuremark.com/

Here is the result (FF 52, FF 57, Chromium 62):

https://ultraimg.com/images/2017/12/05/nr1z.png

In FF (both 52 and 57) there is a visual bug on the 3D rendering test (the reflection highlights on the ball look black). Screenshot:

http://ultraimg.com/images/2017/12/05/nr1x.png

Maybe I should report that to mozilla?

I am also missing the extension which integrates with gnome keyring.

Just info in case someone else is interested in FF 57.

http://peacekeeper.futuremark.com/

Firefox: 8015 Points
Version info:Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0

Chrome: 5812 Points
Version infoMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

https://www.fourmilab.ch/fbench/fbench.html

Firefox:
Running 10000000 iterations.
Elapsed time in seconds: 5.951
Time for 1000 iterations: 0.0006
Microseconds per iteration: 0.5951
No errors in results.

Chrome:
Running 10000000 iterations.
Elapsed time in seconds: 20.978
Time for 1000 iterations: 0.0021
Microseconds per iteration: 2.0978
No errors in results.

I guess video card matters. What is yours?
I am testing with nvidia GTX 680 (with nvidia’s driver)

My results from fbench JS test are:

FF ESR 52.5:

Running 10000000 iterations.
Elapsed time in seconds: 7.948
Time for 1000 iterations: 0.0008
Microseconds per iteration: 0.7948
No errors in results.

FF 57.0.1:

Running 10000000 iterations.
Elapsed time in seconds: 7.650
Time for 1000 iterations: 0.0008
Microseconds per iteration: 0.7650
No errors in results.

Chromium 62:

Running 10000000 iterations.
Elapsed time in seconds: 21.856
Time for 1000 iterations: 0.0022
Microseconds per iteration: 2.1856
No errors in results.

My machine:

erlangen:~ # inxi -F
System:    Host: erlangen Kernel: 4.14.2-1-default x86_64 bits: 64 Console: tty 0
           Distro: openSUSE Tumbleweed 20171203
Machine:   Device: desktop Mobo: ASRock model: Z170 Pro4S serial: M86-64000700034
           UEFI [Legacy]: American Megatrends v: P3.50 date: 06/23/2016
CPU:       Quad core Intel Core i7-6700K (-HT-MCP-) cache: 8192 KB
           clock speeds: max: 4200 MHz 1: 4000 MHz 2: 4000 MHz 3: 4000 MHz 4: 4000 MHz 5: 4000 MHz 6: 4000 MHz
           7: 4000 MHz 8: 4000 MHz
Graphics:  Card: Intel HD Graphics 530
           Display Server: X.Org 1.19.5 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1200@59.95hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) version: 4.5 Mesa 17.2.6
Audio:     Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel Sound: ALSA v: k4.14.2-1-default
Network:   Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e
           IF: enp0s31f6 state: down mac: ...............................
          Card-2: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) driver: ath9k
           IF: wlp3s0 state: up mac: ..............................
Drives:    HDD Total Size: 4512.9GB (43.5% used)
           ID-1: /dev/sda model: WDC_WD40EZRX size: 4000.8GB
           ID-2: /dev/nvme0n1 model: Samsung_SSD_950_PRO_512GB size: 512.1GB
Partition: ID-1: / size: 32G used: 15G (49%) fs: ext4 dev: /dev/nvme0n1p2
           ID-2: /home size: 407G used: 155G (39%) fs: ext4 dev: /dev/nvme0n1p3
           ID-3: swap-1 size: 34.36GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p1
Sensors:   System Temperatures: cpu: 47.5C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 383 Uptime: 17:55 Memory: 7490.3/31863.4MB Client: Shell (bash) inxi: 2.3.40 
erlangen:~ #