Closed Bug 504359 Opened 15 years ago Closed 14 years ago

XULRunner error when trying to update to latest nightly

Categories

(Toolkit :: Application Update, defect)

1.9.1 Branch
x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 523915

People

(Reporter: marcia, Unassigned)

Details

Attachments

(2 files, 1 obsolete file)

Seen while trying to update to the latest Shiretoko nightly.

STR:
1. Have an older Shiretoko nightly present.
2. Perform a manual software update.

Receive the attached error
Please attach your application.ini in the installation directory
Attached file application.ini file (obsolete) —
Attached file application.ini
Attachment #388775 - Attachment is obsolete: true
Summary: XUL error when trying to update to latest nightly → XULRunner error when trying to update to latest nightly
I just updated from
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1pre) Gecko/20090706 Shiretoko/3.5.1pre (.NET CLR 3.5.30729)

to

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1pre) Gecko/20090715 Shiretoko/3.5.1pre (.NET CLR 3.5.30729)

without any problem.

I'll try and older build
Not sure if it matters but the machine does have side by side installs of Firefox 3.5 and Minefield as well.
Was one of the instances running when this happened?
No, I don't believe so.

(In reply to comment #6)
> Was one of the instances running when this happened?
I just went from
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1pre) Gecko/20090614 Shiretoko/3.5pre (.NET CLR 3.5.30729)

to

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1pre) Gecko/20090715 Shiretoko/3.5.1pre (.NET CLR 3.5.30729)

without any problems. Can you try reproducing again?
btw: I also have Minefield installed and tested this while Minefield was also running
are you able to launch Shiretoko successfully after dismissing this dialog? Is this by chance on a VM?
It looked like updater.exe crashed in the middle of an update. I believe there is at least one bug on adding better recovery for the updater and moving to MSI's/MSP's would also likely solve this for Windows.
I suspect this might have bug 523915
No other reports and this was likely caused by bug 523915 so resolving -> duplicate
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: