Closed Bug 458884 Opened 16 years ago Closed 16 years ago

"Run as" dialog prevents autoupdate to FF 3.0.3

Categories

(Firefox :: Installer, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 453693

People

(Reporter: gcklema, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

During an autoupdate to Firefox 3.0.3 (from 3.0.2), a dialog box appears with a asking the user to identify which system user the update should be installed with ("Run as"). 

After selecting the user with admin rights, the dialog disappears and FF fails to restart. Launching FF again shows no update has occurred (still at 3.0.2). A subsequent attempt to update does not download the update. 

Solution: download full version of FF 3.0.3 and install. 

See support forum thread for multiple users who have experienced this problem starting on 10/30/08:
http://support.mozilla.com/tiki-view_forum_thread.php?locale=en-US&comments_parentId=173106&forumId=1

A similar bug I found for Seamonkey:
https://bugzilla.mozilla.org/show_bug.cgi?id=449431

Reproducible: Didn't try

Actual Results:  
FF fails to restart or update to 3.0.3

Expected Results:  
Apply FF 3.0.3 update to version 3.0.2, restart FF, no "Run as" dialog box.
This is most likely fixed on trunk by bug 453693 so duping.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1)
> This is most likely fixed on trunk by bug 453693 so duping.
> 
> *** This bug has been marked as a duplicate of bug 453693 ***

I had this exact problem going from 3.0.4 to 3.0.5 and the only way out was to deinstall/reinstall.

If the bug 453693 fix was supposed to fix this, I believe it is not fixed. I have done a lot of automatic updates and this was the first one that got me the Run As dialog.

If I need to file a separate bug to get this going again, let me know and I will.
If you can still reproduce by installing 3.0.4 and trying to update to 3.0.5 then please do file a bug. I haven't been able to reproduce this and suspect it is an edgecase that is going to be very difficult to diagnose.

btw: the proper component for this if you do file a bug is toolkit -> application update
You need to log in before you can comment on or make changes to this bug.