Package Details: firefox-esr-i18n-cs 128.5.2-1

Git Clone URL: https://aur.archlinux.org/firefox-esr.git (read-only, click to copy)
Package Base: firefox-esr
Description: Standalone web browser from mozilla.org, Extended Support Release
Upstream URL: https://www.mozilla.org/en-US/firefox/enterprise/
Keywords: browser gecko web
Licenses: GPL, MPL, LGPL
Submitter: figue
Maintainer: dudemanguy
Last Packager: dudemanguy
Votes: 48
Popularity: 0.074419
First Submitted: 2015-05-28 23:15 (UTC)
Last Updated: 2024-12-13 15:57 (UTC)

Required by (0)

Sources (100)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 21 Next › Last »

figue commented on 2021-02-27 16:22 (UTC)

In case you want to rebuild firefox-esr with crashreporter (and so, report the tab crash) you can use this PKGBUILD:

https://mirror.lnx.im/archlinux/firefox-esr/78.8.0/PKGBUILD

figue commented on 2021-02-26 22:42 (UTC)

If videos still crash, try to launch firefox with MOZ_DISABLE_CONTENT_SANDBOX=1 variable.

figue commented on 2021-02-23 08:35 (UTC)

@AndyRTR sorry, forgot to push the new patch. It's fixed now.

AndyRTR commented on 2021-02-23 07:09 (UTC)

I see Youtube crashing here also with 78.7.1-2. The new release seems to have broken checksums. Can you please check the sha256sums? I get here d32c87c4526e897d64453914da43f99366d1d0b7d71e43b4027a6cb5aa274040 rust_1.48.patch.gz after a fresh checkout.

figue commented on 2021-02-22 21:59 (UTC)

WARNING: this release has a bug in html5 videos, tabs chash. A possible workaround is to change these properties in about:config (multi-process tabs):

browser.tabs.remote.autostart = false
browser.tabs.remote.autostart.2 = false

Until I figure out why it's crashing and can patch it, stay with previous version or use the workaround.

figue commented on 2021-02-17 18:31 (UTC)

@sp1d3rmxn yeah, it looks like something you describe... I don't know if that port can be changed to another...

In build(), just before "./mach python build/pgo/profileserver.py" you can add this line for instance: sed -e 's/8888/8989/g' -i build/pgo/profileserver.py

and test if it works...

sp1d3rmxn commented on 2021-02-17 18:05 (UTC)

@figure I found what it was, I had to use "watch -n1" to catch it though, yes it was conflicting with port 8888 as you identified in the post. Unfortunately program I am/was using sets up proxy on that port to check updates, etc. but, only when it is setup to use a socks5 proxy.

TLDR; So on my end, a program I was running is intermittently using the port for maintenance to communicate and happened to be running when the build process reached the point of needing to setup its own service on that port.

sp1d3rmxn commented on 2021-02-17 17:59 (UTC)

@figure I was able to build in the chroot and on a virtual machine, so must be something going on with that particular desktop. I will need to dig further on it, probably something weird like bad memory, etc. Apologies for wasting time but, thanks for replying it is appreciated.

figue commented on 2021-02-17 17:11 (UTC)

@sp1d3rmxn that's odd... I said 8080 from memory, but seems 8888, see:

https://fossies.org/linux/firefox/build/pgo/profileserver.py

In any case, I've built firefox-esr hundreds of times, so if 8888 is free there shouldn't be any problem.

sp1d3rmxn commented on 2021-02-17 15:37 (UTC) (edited on 2021-02-17 15:39 (UTC) by sp1d3rmxn)

@figue This is all I have running that is listening (used "sudo netstat -anp | grep LISTEN):

tcp        0      0 127.0.0.1:7080          0.0.0.0:*               LISTEN      327788/ssh          
tcp        0      0 0.0.0.0:5900            0.0.0.0:*               LISTEN      371319/x0vncserver  
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      982/sshd: /usr/bin/ 
tcp        0      0 127.0.0.1:20887         0.0.0.0:*               LISTEN      327788/ssh          
tcp        0      0 127.0.0.1:20888         0.0.0.0:*               LISTEN      420898/autossh.bin

I have seen something similar like this in the past where I have had to use sudo or root privileges to build because of the port assignment being low which I am only thinking because maybe it went random? I am not really sure never saw this before in the years of using this package. As I type this I am building in a chrooted environment to see if the port thing comes up again, either way I will report the result.