335894 - [Win2000] Doesn't restart after downloading to apply update

Status: VERIFIED WORKSFORME

(Toolkit :: Application Update, defect)

Description

[Charli Li (winsxs)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060428 Minefield/3.0a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060428 Minefield/3.0a1

After you update to the next build, and have clicked on "Restart [app]" (i.e. Minefield), the app shuts down completely and doesn't restart and apply the update.  This worked before bug #327140 got filed.

Reproducible: Always

Steps to Reproduce:
1.Use Firefox normally or go to Help > Check for updates.
2.When the confirm restart dialog appears, click "Restart [app]".

Actual Results:  
firefox.exe shuts down completely and does not restart, according to the checks I made in the Windows Task Manager

Expected Results:  
Firefox should restart and apply the update.

This only happens in Windows 2000.  Also, this happened after bug #327140 got partially fixed in the trunk and the Mozilla1.8 branch; can't test if Mozilla1.8 or Mozilla1.8.0 is also affected...

No extensions or anything caused this problem.

Comment 1

[Darin Fisher]

Dave: have you guys tested software update on Win2k?

Comment 2

[Charli Li (winsxs)]

Has this affected the Mozilla1.8 and/or Mozilla1.8.0 branches besides the trunk?

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

I doubt that this is related to 327140, which is to do with server configuration problems in generating updates rather than client problems. 

Have you tried updating since bug 332088 was fixed ? You'd need a nightly more recent than 20060419 for that.

Why can't you test a Mozilla1.8 build ?

Comment 4

[Charli Li (winsxs)]

(In reply to comment #3)
> Have you tried updating since bug 332088 was fixed ? You'd need a nightly more
> recent than 20060419 for that.
My nightly is 20060430
> Why can't you test a Mozilla1.8 build ?
> 
Two reasons why:
1.The only Mozilla1.8 build I have is on my other computer, which is WINNT 5.1 (Windows XP).
2.The latest Mozilla1.8 build version is 2.0a1; I like to use newer software, so that's why I ordiarily use the Trunk (3.0a1)

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

Was the file <firefox install dir>\updates\last-update.log last modified at the time of your last update attempt ? If so, please attach it to this bug.

Comment 6

[Charli Li (winsxs)]

Attachment: last-update.log requested by Nick

Comment 7

[Charli Li (winsxs)]

Comment on attachment 220442 [details]
last-update.log requested by Nick

Here's the last-update.log that you requested, Nick.  It was updated after I downloaded an update that offered a build ID along with Minefield 3.0a1

Comment 8

[Nick Thomas [:nthomas] (UTC+12)]

Ok, that looks like a successful update. Updating bug summary.

Comment 9

[Charli Li (winsxs)]

Steve, did this happen to you after bug #327140 was partially fixed on the trunk and Mozilla1.8?

Comment 10

[Charli Li (winsxs)]

OK, never mind.  Sorry about the spam.

P.S.  this happened to me again when I was updating to 20060504.

Comment 11

[Charli Li (winsxs)]

Updating bug summary since it has nothing to do with the update application, it has to do with startup issues after the update has downloaded.

Comment 12

[Nick Thomas [:nthomas] (UTC+12)]

To the best of my knowledge, the most common process is:
1, <app> downloads update
2, <app> requests restart
3, <user> agrees to that
4, <app> closes and spawns updater
5, updater does it's thing (for better or worse), and writes updates\last-update.log
6, updater spawns <app>

From the information you have given, everything goes fine until step 6, and therefore your bug-summary change is incorrect.

Put another way, does the BuildID change after you have had to start up Firefox manually ?

Comment 13

[Charli Li (winsxs)]

(In reply to comment #12)
> To the best of my knowledge, the most common process is:
> 1, <app> downloads update
> 2, <app> requests restart
> 3, <user> agrees to that
> 4, <app> closes and spawns updater
> 5, updater does it's thing (for better or worse), and writes
> updates\last-update.log
> 6, updater spawns <app>
> 
> From the information you have given, everything goes fine until step 6, and
> therefore your bug-summary change is incorrect.
> 
> Put another way, does the BuildID change after you have had to start up Firefox
> manually ?
> 

Actually, everything is fine until step 4, when the app closes, but doesn't spawn the updater.  I would have to start fx manually (using the QuickLaunch shortcut), and then the app (after I manually start it) spawns updater, and does its thing during step 5 through 6.

And yes, the build ID does change.

Comment 14

[Nick Thomas [:nthomas] (UTC+12)]

Ok, pardon me. At this point it would be very useful to see if a Mozilla1.8 build does the same thing. 

Please get a build from 
 http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2006-05-06-04-mozilla1.8/
install it in a new directory, and see if it restarts properly.

Comment 15

[Charli Li (winsxs)]

(In reply to comment #14)
> Ok, pardon me. At this point it would be very useful to see if a Mozilla1.8
> build does the same thing. 
> 
> Please get a build from 
> 
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2006-05-06-04-mozilla1.8/
> install it in a new directory, and see if it restarts properly.
> 

Does not happen on Mozilla1.8; testing Mozilla1.8.0...

Comment 16

[Charli Li (winsxs)]

(In reply to comment #15)
> (In reply to comment #14)
> > Ok, pardon me. At this point it would be very useful to see if a Mozilla1.8
> > build does the same thing. 
> > 
> > Please get a build from 
> > 
> > http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2006-05-06-04-mozilla1.8/
> > install it in a new directory, and see if it restarts properly.
> > 
> 
> Does not happen on Mozilla1.8; testing Mozilla1.8.0...
> 

Mozilla1.8.0 doesn't check for updates; remember bug #327140??

Comment 17

[Charli Li (winsxs)]

(In reply to comment #15)
> 
> Does not happen on Mozilla1.8; testing Mozilla1.8.0...
> 

Whoops, I meant "it restarts properly on Mozilla1.8".

Comment 18

[Charli Li (winsxs)]

Fixed from updating to 2006051706