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)
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
Comment 1•15 years ago
|
||
Please attach your application.ini in the installation directory
Reporter | ||
Comment 2•15 years ago
|
||
Comment 3•15 years ago
|
||
Attachment #388775 -
Attachment is obsolete: true
Updated•15 years ago
|
Summary: XUL error when trying to update to latest nightly → XULRunner error when trying to update to latest nightly
Comment 4•15 years ago
|
||
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
Reporter | ||
Comment 5•15 years ago
|
||
Not sure if it matters but the machine does have side by side installs of Firefox 3.5 and Minefield as well.
Comment 6•15 years ago
|
||
Was one of the instances running when this happened?
Reporter | ||
Comment 7•15 years ago
|
||
No, I don't believe so. (In reply to comment #6) > Was one of the instances running when this happened?
Comment 8•15 years ago
|
||
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?
Comment 9•15 years ago
|
||
btw: I also have Minefield installed and tested this while Minefield was also running
Comment 10•15 years ago
|
||
are you able to launch Shiretoko successfully after dismissing this dialog? Is this by chance on a VM?
Comment 11•15 years ago
|
||
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.
Comment 12•15 years ago
|
||
I suspect this might have bug 523915
Comment 13•14 years ago
|
||
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.
Description
•