I just updated the "critical" firefox update, and it is *seriously* buggy.
1. I killed my old session, and started a new. Many (all?) tabs show *nothing* until I put my cursor in the URL bar and hit <enter> 2. I cannot open a link in an email in thunderbird. I click the link, and after a bit (30 sec? more?) a small windows tells me that firefox is running, but not responding, which it certainly responds when I focus on firefox.
mark
On Thu, Jul 12, 2018 at 10:36:55AM -0400, mark wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
no issue on my side: yum -y update firefox firefox -> File -> Quit started firefox -> tabs restored
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter>
maybe a side effect of "killing"?
- I cannot open a link in an email in thunderbird.
I don't use thunderbird, but right-click+"Open link" from a gnome-terminal under an url works fine for me.
YMMV
Tru
On 07/12/2018 09:36 AM, mark wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter> 2. I cannot open a link in an email in thunderbird. I click the link, and after a bit (30 sec? more?) a small windows tells me that firefox is running, but not responding, which it certainly responds when I focus on firefox.
mark
I have no issues with tabs.
Firefox links work fine too.
On 07/12/2018 04:05 PM, Johnny Hughes wrote:
On 07/12/2018 09:36 AM, mark wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter> 2. I cannot open a link in an email in thunderbird. I click the link, and after a bit (30 sec? more?) a small windows tells me that firefox is running, but not responding, which it certainly responds when I focus on firefox.
markI have no issues with tabs.
Firefox links work fine too.
I meant email links into the default firefox browser from thunderbird.
Johnny Hughes wrote:
On 07/12/2018 04:05 PM, Johnny Hughes wrote:
On 07/12/2018 09:36 AM, mark wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter> 2. I cannot open a link in an email in thunderbird. I click the link, and after a bit (30 sec? more?) a small windows tells me that firefox is running, but not responding, which it certainly responds when I focus on firefox.
mark
I have no issues with tabs.
Firefox links work fine too.
I meant email links into the default firefox browser from thunderbird.
Um, my update gave me 60.1.0esr, which I see from your other email is in testing.
Not sure how I got that...
mark
On 07/12/2018 04:14 PM, mark wrote:
Johnny Hughes wrote:
On 07/12/2018 04:05 PM, Johnny Hughes wrote:
On 07/12/2018 09:36 AM, mark wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter> 2. I cannot open a link in an email in thunderbird. I click the link, and after a bit (30 sec? more?) a small windows tells me that firefox is running, but not responding, which it certainly responds when I focus on firefox.
mark
I have no issues with tabs.
Firefox links work fine too.
I meant email links into the default firefox browser from thunderbird.
Um, my update gave me 60.1.0esr, which I see from your other email is in testing.
Not sure how I got that...
mark
That is now the released version .. and 'it works for me'.
Le 12/07/2018 à 16:36, mark a écrit :
I just updated the "critical" firefox update, and it is *seriously* buggy.
I just upgraded Firefox on a sandbox installation, and here's what I noticed so far.
1. On startup, the whole window is black for 1 - 2 seconds, and then Firefox displays OK.
2. Firefox is in english, though my whole system is in French, so I guess translation files are messed up.
Here's just an idea. Why not put Firefox in the CR repository while working out issues this sort of issues?
Cheers,
Niki
On 07/13/2018 02:36 AM, Nicolas Kovacs wrote:
Le 12/07/2018 à 16:36, mark a écrit :
I just updated the "critical" firefox update, and it is *seriously* buggy.
I just upgraded Firefox on a sandbox installation, and here's what I noticed so far.
- On startup, the whole window is black for 1 - 2 seconds, and then
Firefox displays OK.
- Firefox is in english, though my whole system is in French, so I
guess translation files are messed up.
Here's just an idea. Why not put Firefox in the CR repository while working out issues this sort of issues?
Well .. it is working like the upstream one, that's why its released.
If we knew about any bugs other than ones that also exist in the RHEL compile, we would not release it at all, we'd fix it.
Johnny Hughes wrote:
On 07/13/2018 02:36 AM, Nicolas Kovacs wrote:
Le 12/07/2018 à 16:36, mark a écrit :
I just updated the "critical" firefox update, and it is *seriously* buggy.
<snip>
Well .. it is working like the upstream one, that's why its released.
If we knew about any bugs other than ones that also exist in the RHEL compile, we would not release it at all, we'd fix it.
Ok... first, let me say that I'm anal, and log out of my workstation, not just lock the screen, when I leave for the day, so *everything* I have running should be shut down.
Now, here's my observations: I see four firefox processes running now. I have two windows open, but there's also the original root of them (firefox -P --no-remote). I can understand two other processes, since I have to firefox windows open, but I don't know why I have three.
mark
On 07/13/2018 09:03 AM, mark wrote:
Johnny Hughes wrote:
On 07/13/2018 02:36 AM, Nicolas Kovacs wrote:
Le 12/07/2018 à 16:36, mark a écrit :
I just updated the "critical" firefox update, and it is *seriously* buggy.
<snip>
Well .. it is working like the upstream one, that's why its released.
If we knew about any bugs other than ones that also exist in the RHEL compile, we would not release it at all, we'd fix it.
Ok... first, let me say that I'm anal, and log out of my workstation, not just lock the screen, when I leave for the day, so *everything* I have running should be shut down.
Now, here's my observations: I see four firefox processes running now. I have two windows open, but there's also the original root of them (firefox -P --no-remote). I can understand two other processes, since I have to firefox windows open, but I don't know why I have three.
Looking at this now .. here is how it appears to work:
there is a wrapper ..
/usr/lib64/firefox/firefox
That is one process .. and it starts the rest ========================================== then there is a process called:
-childID 1
That seems to be the main broswer process .. all the things besides the actual TABS.
===========================================
Then each tab you open spawns a seperate process .. so the first TAB (that is your home page) spawns a process with '-childID 2'
============================================
Other tabs seem to spawn an other new '-childID <X>'
So, it seems that the main process and the '-childID 1' process stay forever // and some of the other Child processes start and stop as required.
if you do ps -ef | grep firefox, you can get info on the processes .. and I an certainly not an expert .. but I don't see any issues.
Johnny Hughes wrote:
On 07/13/2018 09:03 AM, mark wrote:
Johnny Hughes wrote:
On 07/13/2018 02:36 AM, Nicolas Kovacs wrote:
Le 12/07/2018 à 16:36, mark a écrit :
I just updated the "critical" firefox update, and it is *seriously* buggy.
<snip>
Ok... first, let me say that I'm anal, and log out of my workstation, not just lock the screen, when I leave for the day, so *everything* I have running should be shut down.
Now, here's my observations: I see four firefox processes running now. I have two windows open, but there's also the original root of them (firefox -P --no-remote). I can understand two other processes, since I have to> firefox windows open, but I don't know why I have three.
Looking at this now .. here is how it appears to work: there is a wrapper ..
/usr/lib64/firefox/firefox
That is one process .. and it starts the rest
then there is a process called:
-childID 1
That seems to be the main broswer process .. all the things besides the actual TABS. =========================================== Then each tab you open spawns a seperate process .. so the first TAB (that is your home page) spawns a process with '-childID 2' ============================================ Other tabs seem to spawn an other new '-childID <X>'
So, it seems that the main process and the '-childID 1' process stay forever // and some of the other Child processes start and stop as required.
if you do ps -ef | grep firefox, you can get info on the processes .. and I an certainly not an expert .. but I don't see any issues.
I just saw something, maybe on slashdot, that chrome was doing that, to try to prevent malware on one site slipping itself to another tab. But I've to many, many tabs, so I'm not sure why only three processes, if that's the case. Also, that suggests that t-bird's trying to start a new tab in the wrong process.
mark
On 13/07/18 13:09, Johnny Hughes wrote:
On 07/13/2018 02:36 AM, Nicolas Kovacs wrote:
Le 12/07/2018 à 16:36, mark a écrit :
I just updated the "critical" firefox update, and it is *seriously* buggy.
I just upgraded Firefox on a sandbox installation, and here's what I noticed so far.
- On startup, the whole window is black for 1 - 2 seconds, and then
Firefox displays OK.
- Firefox is in english, though my whole system is in French, so I
guess translation files are messed up.
Here's just an idea. Why not put Firefox in the CR repository while working out issues this sort of issues?
Well .. it is working like the upstream one, that's why its released.
If we knew about any bugs other than ones that also exist in the RHEL compile, we would not release it at all, we'd fix it.
I can confirm the same behaviour Mark describes in point (1) above on a genuine RHEL7 system, so as Johnny says, "it is working like the upstream one", so no bug there from a CentOS perspective. However, it's not consistent (for me) and not troublesome enough for me to have taken note as to when it may or may not occur.
I am not able to meaningfully comment on point (2).
On Fri, Jul 13, 2018 at 09:36:52AM +0200, Nicolas Kovacs wrote:
Le 12/07/2018 à 16:36, mark a écrit :
I just updated the "critical" firefox update, and it is *seriously* buggy.
I just upgraded Firefox on a sandbox installation, and here's what I noticed so far.
- On startup, the whole window is black for 1 - 2 seconds, and then
Firefox displays OK.
- Firefox is in english, though my whole system is in French, so I
guess translation files are messed up.
I can't reproduce your issue.
switching from en_US to fr_FR is just a matter of: $ export LANG=fr_FR.UTF-8 $ firefox or $ export LANG=en_US.UTF-8 $ firefox
1) just make sure that you don't have another firefox in the background. 2) the profile manager is in English but the browser starts with the localised langage.
YMMV
Cheers
Tru
On 07/12/2018 07:36 AM, mark wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter> 2. I cannot open a link in an email in thunderbird. I click the link, and after a bit (30 sec? more?) a small windows tells me that firefox is running, but not responding, which it certainly responds when I focus on firefox.
mark
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
You can try running 'firefox -safe-mode' to see if you have a problem with installed extensions. Also, you can create a new profile (and stlil leave the old one there), to see if your profile database is corrupt. These are both problems that come up with both firefox and thunderbird.
Nataraj
Hello,
On Thu, 12 Jul 2018 10:36:55 -0400 "mark" m.roth@5-cent.us wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter>
[snip]
I reproduced this 1. point. I also lost all my tab groups, ouch. This an zillion extensions are not available anymore. I've just reverted to v52 and added an exclude=firefox line to the repo file in yum config :-), I seriously don't understand how they could decide to switch to the webextension thing like that.
Regards,
My FF 60 just crashed randomly when ever it feels liek it. ive since rolled back to older stable versions until community says its now stable.
On 07/27/2018 03:37 PM, wwp wrote:
Hello,
On Thu, 12 Jul 2018 10:36:55 -0400 "mark" m.roth@5-cent.usmailto:m.roth@5-cent.us wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
1. I killed my old session, and started a new. Many (all?) tabs show *nothing* until I put my cursor in the URL bar and hit <enter>
[snip]
I reproduced this 1. point. I also lost all my tab groups, ouch. This an zillion extensions are not available anymore. I've just reverted to v52 and added an exclude=firefox line to the repo file in yum config :-), I seriously don't understand how they could decide to switch to the webextension thing like that.
Regards,
_______________________________________________ CentOS mailing list CentOS@centos.orgmailto:CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Promise Kumalo wrote:
My FF 60 just crashed randomly when ever it feels liek it. ive since rolled back to older stable versions until community says its now stable.
I've rolled it back on my workstation, and am *not* rolling it out to users. For one, thunderbird can't talk to the correct thread, if I click a link, and some web pages *eat* the system - firefox is frozen for minutes. Back to 52.x, no problems. And I run noscript, so no ad links.
mark
On 07/27/2018 03:37 PM, wwp wrote:
Hello,
On Thu, 12 Jul 2018 10:36:55 -0400 "mark" m.roth@5-cent.usmailto:m.roth@5-cent.us wrote:
I just updated the "critical" firefox update, and it is *seriously* buggy.
- I killed my old session, and started a new. Many (all?) tabs show
*nothing* until I put my cursor in the URL bar and hit <enter>
[snip]
I reproduced this 1. point. I also lost all my tab groups, ouch. This an zillion extensions are not available anymore. I've just reverted to v52 and added an exclude=firefox line to the repo file in yum config :-), I seriously don't understand how they could decide to switch to the webextension thing like that.
Regards,
CentOS mailing list CentOS@centos.orgmailto:CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
-
Johnny Hughes -
mark -
Nataraj -
Nicolas Kovacs -
Phil Perry -
Promise Kumalo -
Tru Huynh -
wwp