Closed
Bug 131351
Opened 24 years ago
Closed 24 years ago
XML Parsing Error undefined entity in createProfileWizard.xul
Categories
(SeaMonkey :: Startup & Profiles, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bugzilla.mozilla.org, Assigned: bugs)
References
Details
(Keywords: smoketest)
I get this when I start the latest nightly. I'd tell you the version but I
can't start it :)
XML Parsing Error: undefined entity
Location: chrome://communiator/content/profile/createProfileWizard.xul
Line Number 15, Column 1:
<window title="&newprofile.title;" orient="vertical"
^
Not happening with 2002030908. But there are no changes to
createProfileWizard.xul that I can see either.
| Reporter | ||
Comment 1•24 years ago
|
||
I should have mentioned - I'm using the -P (username) switch. Each time I start
with a new nightly Moz asks me to set up my profile again, which is why it's
looking at createProfileWizard.xul at all.
Comment 2•24 years ago
|
||
profile manager
Assignee: asa → ben
Severity: normal → critical
Component: Browser-General → Profile Manager FrontEnd
QA Contact: doronr → ktrina
Comment 3•24 years ago
|
||
I get a similar problem with the builds from the last day or so on Windows XP
(just tried it with 2002031503).
"
XML Parsing Error: undefined entity
Location: chrome://communicator/content/profile/profileSelection.xul
Line Number 42, Column 1:
<window
^
"
This isn't using any execution switches. I have two profiles in my install.
Comment 4•24 years ago
|
||
I get a similar problem with the builds from the last day or so on Windows XP
(just tried it with 2002031503).
"
XML Parsing Error: undefined entity
Location: chrome://communicator/content/profile/profileSelection.xul
Line Number 42, Column 1:
<window
^
"
This isn't using any execution switches. I have two profiles in my install.
Comment 5•24 years ago
|
||
I just ran into this. I no "start" or "exit" buttons, no profiles listed. No
good way to either exit mozilla or start it.
confirming, setting OS to all (I'm seeing this on Linux), upgrading to blocker.
Severity: critical → blocker
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: smoketest
OS: Windows 2000 → All
Hardware: PC → All
Comment 6•24 years ago
|
||
As a note, I have no localizations of any kind installed. I'm seeing this with
a debug build pulled at "Fri Mar 15 15:00:18 EST 2002"
Comment 7•24 years ago
|
||
To add to the mystery:
1) I see this in a debug build
2) I do not see this in another debug build pulled by date for the exact same
date
3) I reverted all local changes I had in the build I was seeing this with,
removed component.reg, rebuilt, restarted. Same problem.
Something is not getting packaged right....
| Reporter | ||
Comment 8•24 years ago
|
||
That seems to be correct - I was using a talkback build. No problems with the
latest nightly 2002031608 (non-talkback build).
Comment 9•24 years ago
|
||
Here is the best part. I clobbered and the problem is now gone. Interestingly
enough, the profile manager now comes up in Modern instead of Classic. What
could have triggered that, and is it related to this?
Based on comments looks like this is now worksforme. If not, please reopen...
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 12•24 years ago
|
||
Um... This "worksforme" because I build and I clobbered? What about all the
people reporting this with downloaded packaged builds (RPM, installer, zip, all
are represented). Maybe all the build systems in question just need to clobber,
but if that is the case they should _do_ so.
Comment 13•24 years ago
|
||
I still see this bug using today's build.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Comment 14•24 years ago
|
||
This has the profile wizard completely unusable in todays windows commercial
build 2002-03-19-05-trunk
-No existing profiles are recognized nor can I create a new profile. further
testing of app is impossible.
BLOCKER!!!
I only see this on windows. mac builds and linux is fine.
OS: All → Windows 98
Hardware: All → PC
Comment 15•24 years ago
|
||
The work-around described in bug 131061, namely removing all occurrences of
embed.jar from installed-chrome.txt, should also fix this. That should
hopefully allow this bug to be downgraded from a blocker.
Comment 16•24 years ago
|
||
When I came across this problem (no profile is listed and no start/exit
button), I looked up bugzilla and came here. On reading Boris' comment
that the problem had gone after clobbering and rebuilding, I did the
same, but my debug build (I pulled the tree this morning around 2am
Pacfic time) still has the problem. No profile is listed and
there's no start/exit button. When I press 'Manage profile' button
(which is only button available) and 'create profile' button in
the next step, I got another dialog box in which I'm told to
press 'next button' to go ahead, but 'next button' is not there.
The error messages I'm getting is different, though. So, I'm not
sure I'm seeing the same problem as reported here.
Javascript error:
chrome://communicator/content/profile/profileSelection.js line 273:
doSetOKCancel is not defined
Javascript error:
chrome://communicator/content/profile/createProfileWizard.js line 63:
movetoAlertPosition is not defined
Javascript error:
chrome://global/content/wizardHandlerSet.js line 114: oParentNextButton
has no properties
WARNING: Weired, we're finalized with a null mJSObject?, file
E:\Works\moz\mozilla\dom\src\base/nsGlobalWindow.cpp line 750
BTW, I looked into installed-chrome.txt, but there's not a single line
with 'embed.jar' in my case. Anyway, what's the correct bug number
in which that fix was suggested? bug 131061 is about a different issue.
Comment 17•24 years ago
|
||
WFM for a fetch and build I did a few hours ago. I fetched, did a dependency
check and built using nmake over my existing build.
Comment 18•24 years ago
|
||
I think this is very much related to bug 131016 - string comparisons were broken
at a very low level last night, and it had many repercussions, including making
overlays fail to load. I'm also not seeing a problem, marking WORSKFORME
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 19•24 years ago
|
||
I can't reproduce this in the tree I pulled couple of hours ago. W2K
Comment 20•24 years ago
|
||
I still see this. I'm on XP.
Comment 21•24 years ago
|
||
as of the latest depend build on windows this also wfm (build
2002-03-19-10-trunk)
verified
Status: RESOLVED → VERIFIED
Comment 22•24 years ago
|
||
After updating my local tree, I rebuilt it and it also works for me under Win2k.
Comment 23•24 years ago
|
||
I'm still seeing this on Windows 2000, I've clobbered my profile directory and
the mozilla directory prior to downloading and installing:
http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32.zip
which is currently dated on the server to 20-Mar-2002 11:55
I don't know if it makes any difference but I have Netscape Communicator 4.7X
installed so it should ask me if I want to convert that profile.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Can anyone reproduce this in a build from 2002-03-21-02 or later? If not, then
it's probably a duplicate, as comment 24 says.
Comment 26•24 years ago
|
||
Fixed by checkin for bug 131016. Latest nightly doesn't show this problem.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 27•24 years ago
|
||
I haven't seen this with recent builds including today 2002-03-21-10-trunk
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•