Closed
Bug 268664
Opened 20 years ago
Closed 20 years ago
XML Parsing Error, Upgrading from .9pr to 1.0 results in a dead browser.
Categories
(Firefox :: Installer, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 246623
People
(Reporter: dkaiser, Assigned: bugs)
Details
Attachments
(1 file)
24.95 KB,
image/pjpeg
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: 1.0 Nov 11th I tried to upgrade by clicking on the red ^ icon. It downloaded 1.0, tried to install and the browser crashed. I restarted the PC and now everytime I try to start Firefox, I see this error... XML Parsing Error: undefined entity Location chrome://browser/content/browser.xul Line Number 910, Column 33: chromedir="locale.dir;">__________^ Reproducible: Didn't try Steps to Reproduce: 1.Have 6 tabs open 2.Click the red ^ upgrade button and upgrade from 1.0pr to 1.0 3. Actual Results: I can't uninstall Mozilla now. Do I delete the dir and try again or install over it? Expected Results: Upgraded to todays 1.0 release. Safe mode doesn't work.
My system info -> http://servoe.com/sys.txt (save as)
Summary: XML Parsing Error, Upgrading from 1.0pr to 1.0 results in a dead browser. → XML Parsing Error, Upgrading from .9pr to 1.0 results in a dead browser.
I've got the exact same error after trying to use the auto updater to upgrade from PR1 to 1.0. XML Parsing Error: undefined entity Location: chrome://browser/content/browser.xul Line Number 910, column 33: chromedir="&locale.dir;"> ---------------------------------^ After downloading the latest nightly build and installing, this is the error I get: firefox.exe - entry point not found The procedure entry point ??1nsCOMPtr_base@@QAE@XZ could not be located in the dynamic link library xpcom.dll. I think the feedback agent report number on the original crash is TB1876514Z if it helps.
Comment 4•20 years ago
|
||
*** This bug has been marked as a duplicate of 246623 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → installer
You need to log in
before you can comment on or make changes to this bug.
Description
•