454659 - 2.0 to 2.0.0.17 Update Hangs Firefox on Restart

Status: RESOLVED WORKSFORME

(Toolkit :: Application Update, defect)

Description

[Al Billings [:abillings - ex-MoCo]]

I found that when 2.0 is updated to 2.0.0.17, which uses the complete update option, that when the user tells the browser to restart after downloading the update, Firefox will hang. It sits there, using 0% CPU, and does nothing.

If the user stops the process and then starts Firefox again, the update will then install.

I've done this three times, all on Ubuntu 8.04 using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/2006101022 Firefox/2.0 and going to Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.17) Gecko/2008082909 Firefox/2.0.0.17.

Comment 1

[Al Billings [:abillings - ex-MoCo]]

This also reproduces with a current Ubuntu 7.10 VM.

JuanB's VMs are not as up to date and he had no problem with 8.04. I suspect a conflict from a recently updated package from the Ubuntu repositories.

Comment 2

[juan becerra [:juanb]]

This worked for me on an older VM (Ubuntu 8.04); I updated my older 8.04 Ubuntu VM using their update manager, and now the system is "up to date." The update from 2.0-20017 on beta still works fine for me.

Could there have been a problem in generating the reference VM that the QA team uses?

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

Attachment: Output of "strace ./firefox" on Ubuntu 8.04 reference VM, Firefox 2.0 -> 2.0.0.17

Comment 4

[juan becerra [:juanb]]

I've tested another distribution (Mint) that's about a month old, and I was able to reproduce the problem as seen by abillings. I then updated the vm so that it was up to date, and I continue to see the problem where after the update is applied the application does not restart.

Comment 5

[juan becerra [:juanb]]

Now I tried to get an update on the Mint machine, from Fx2.0 to Fx20016 on "release", and the update works. So it might not be a problem with the VM.

Comment 6

[juan becerra [:juanb]]

I have tried again on the same Mint machine on the "betatest" and "beta" channels going from Fx2.0 - Fx20017 and it worked. I had a couple of people check, again, and for at least one person the app does not restart after the update, and for another person it does.

Dunno what's going on here.

Comment 7

[Robert Strong (they/them - no direct email)]

I don't believe that the code paths for Linux have changed in quite some time so this may be difficult to track down. Not sure what is going on here either

Comment 8

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

- does this happen for all "complete" updates, or if there is something special about FF2.0? For example, does FF2.0.1 -> FF2.0.0.17 work or fail? 

- does this happen for en-US only or other locales?

- does this happen on a physical machine running same version of ubuntu as the "mint" VM?

We just started our beta period this morning, so I'll be curious if any beta users hit this in the coming days...

Comment 9

[Carsten Book [:Tomcat]]

(In reply to comment #8)
> - does this happen for all "complete" updates, or if there is something special
> about FF2.0? For example, does FF2.0.1 -> FF2.0.0.17 work or fail? 
> 
Hi,

so i did some tests and i can reproduce this Problem with 2.0.0.0 and my Ubuntu VM (its not the QA VM, its my personal setup one, so its a Problem on Ubuntu).

But:

-> The Problem seems NOT related to this Update to 2.0.0.17 beta, you can see this Problem (no clean shutdown of Firefox) also i you use Firefox 2.0.0.0 and browse to some sites and then try to exit Firefox,
and a quick Test on Firefox 2.0.0.10->2.0.0.17 was fine.

So maybe its something in Firefox 2.0.0.0 and Ubuntu that conflict ? But at least it seems no Update Bug :)
 

> We just started our beta period this morning, so I'll be curious if any beta
> users hit this in the coming days...

Depend also how many users use still 2.0 and are on the Beta Program. So far there are no reports.

Comment 10

[Al Billings [:abillings - ex-MoCo]]

(In reply to comment #8)
> - does this happen for all "complete" updates, or if there is something special
> about FF2.0? For example, does FF2.0.1 -> FF2.0.0.17 work or fail? 

This was asked yesterday. It is not all complete updates, only from 2.0 explicitly. We test complete updates on later releases (I used 2.0.0.15) and there were no problems.
 
> - does this happen for en-US only or other locales?

 I only tested with en-US.
 
> - does this happen on a physical machine running same version of ubuntu as the
> "mint" VM?

 We have no physical machines with Ubuntu so this is hard to test. QA's Linux boxes are all VMs except for servers running CentOS. This shouldn't make a difference though.

Our best guess it is some weird timing issue with 2.0 doing something and refusing to allow itself to be shut down when the update restart is selected. If you end the process when it fails to restart and start Firefox, the update will apply itself normally.

Comment 11

[Robert Strong (they/them - no direct email)]

No progress on identifying the cause and since this affected updating from Firefox 2.0 which is no longer supported while newer versions of Firefox didn't exhibit this problem I'm resolving this as wfm