287783 - Canceling update to 1.0.2 causes FF to crash and must be re-installed

Status: RESOLVED DUPLICATE of bug 283680

(Toolkit :: Application Update, defect)

Description

[Johan Soderstrom]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

When updating Firefox through the automatic updater but pressing Cancel at the
last (?) step Firefox will not handle this situation correctly. Sadly I did not
make any screenshots. This maked firefox unable to start (ever - for me at
least) when closed. A reinstall was needed... This is why I label this bug as
critical - even though I think I'm the only one affected because people just
don't press Cancel there!!!


Reproducible: Always

Steps to Reproduce:
1. I pressed the updater icon
2. I pressed install.
3. I went through 3-4 steps (can't remember how many, sorry) but I do know I
pressed Cancel at one point. As far as I can rememer it was when the last
quastion "Should I install this" or something like that popped up...
4. I still wanted the update, but the update icon was missing, so I restarted
firefox (tried to)...
Actual Results:  
Result: firefox tells me that "??? is still running and I need to close the
application for the update to finish" or something like that, again I'm sorry I
wasn't paying attention... Note that no error was reported, so this is all I can
give you guys...

Dirty fix: Download the entire installer and re-install everything...

Well, I think that I'm the only one stupid enough to press cancel at that stage,
so this is probably a bug that you'll only see once... BUT on the other hand it
rendered firefox unusuable...

Expected Results:  
It should have started up as normal.... or something... not hanging

Comment 1

[:Gavin Sharp [email: [e-mail]]]

I've seen the same behavior. To get Firefox working again, delete the
"xpicleanup.dat" file in your program directory.

Comment 2

[:Gavin Sharp [email: [e-mail]]]

See bug 283680 comment 14.

*** This bug has been marked as a duplicate of 283680 ***