Closed
Bug 122834
Opened 23 years ago
Closed 23 years ago
XML Parsing error starting mozilla
Categories
(SeaMonkey :: Startup & Profiles, defect)
Tracking
(Not tracked)
CLOSED
WORKSFORME
People
(Reporter: bobbell, Assigned: bugs)
References
Details
Starting mozilla without a ~/.mozilla directory, but with a ~/.netscape
directory yields a window with the following text:
XML Parsing Error: undefined entity
Location: chrome://communicator/content/profile/profileSelection.xul?manage=true
Line Number 42, Column 1:
<window
^
This appears to be in reference to line 42 of the file
content/communicator/profile/profileSelection.xul from chrome/comm.jar, or
profile/resources/content/profileSelection.xul in the source tree.
This problem was produced on 2002013013.
Comment 1•23 years ago
|
||
-> profile
Assignee: hewitt → ben
Component: Themes → Profile Manager FrontEnd
QA Contact: pmac → ktrina
Comment 2•23 years ago
|
||
Got same behaviour on win98 20020315 after chopping as usual the "mozilla" dir
in "Application Data" before unzipping the new nightly build.
A slightly older build works.
Comment 3•23 years ago
|
||
Reporter,
Are you still seeing this on recent nightly? If so, please reopen,
marking wfm
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Comment 4•23 years ago
|
||
Verified WFM. To be reopened if problem still occurs.
Status: RESOLVED → VERIFIED
For the record, this problem does not reoccur with Mozilla 1.1a.
Status: VERIFIED → CLOSED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•