Closed Bug 286252 Opened 19 years ago Closed 19 years ago

After new nightly install minimal error window on warpzilla load

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
OS/2
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mike.hitchcock, Unassigned)

Details

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8b2) Gecko/20050307
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8b2) Gecko/20050307

After downloading and intalling nightly MOZILLA-OS2-INSTALLER.EXE dated 14th
march 2005 on loading only minimal title bar with one line of page displays with
following error line:-

XML PARSING ERROR: undefined entity Location:
chrome://navigator/content/navigator.zul Line Number 63, column 1:<window
id="main-window"

Reproducible: Always

Steps to Reproduce:
1.run warpzilla from icon
2.
3.

Actual Results:  
error as described above. Browser will not load

Expected Results:  
Bring up browser
Strange. It's working for me. Did you install it over another build?
Yes I installed it over the previous nightly build - I will try a clean install.
Tried a clean install but got the same message with an addition - after
"main-window" <broadcaster id="Comunicator WorkMode"
Zip version of 14th build has been up working fine over 23 hours for me.
This report deals with something that is arguably outside the remit of Bugzilla,
however I see it quite often in self-built lizards when the chrome is messed up.

What is the correct way to diagnose and fix problems like this?

I appreciate that if one follows the instructions to the letter, it will not
happen (per comment 4).

I would work on the basis that the installation is missing a .dtd file or
something else is preventing the xml parser completing the parse of the xul:
Is there a way of finding out where the problem is occuring.

Despite comment 3, the odds really are that a completely fresh install
(perhaps as a different user) will leave you with a working lizard.
I tried a new install but with pretty much the same error. I must stress that I
have been installing nightly builds on a regular basis without this problem. The
envionment(AMD 233 128mb Warp 4 fp 15) has not changed and if I revert to a
previous nightly it loads and runs fine.(this report is being done on a reloaded
previous nightly) so it is something in the current build that is wrong.
Did you try a new profile?
No - It never gets that far - it shows the Mozilla logo then loads a minimal
screen with only a strip with a title bar and only one line underneath with the
error message.

What I have done is to do a new download and install with the MOZILLA_HOME and
MOZ_PLUGIN_PATH iin Config,sys remmed out which should force an entirely new
setup on load. Unfortunately to no avail - still get same error message
Version: unspecified → Trunk
(In reply to comment #8)
> No - It never gets that far - it shows the Mozilla logo then loads a minimal
> screen with only a strip with a title bar and only one line underneath with the
> error message.
> 
> What I have done is to do a new download and install with the MOZILLA_HOME and
> MOZ_PLUGIN_PATH iin Config,sys remmed out which should force an entirely new
> setup on load. Unfortunately to no avail - still get same error message

Had the same problem under win when trying to test my langpack.
What solved this for me (before switching extensions/themes broke) was a clean
install with the chrome dir deleted in both program dir and profile dir after
uninstallation of previous version.

Tried a clean install on another system - IBM Thinkpad 600x OS/2 Warp 4 fp 15.
Got exactly the same result - same error without loading browser.
Mike Hitchcock, just to make sure:
After you install into a clean directory and do not start the program, there
should be no Mozilla directory in the installation dir next to mozilla.exe. When
you then unset MOZILLA_HOME it should create this Mozilla directory and a fresh
profile. Does it happen like this for you?
This bug continues on all OS/2 installer nightlies but it is noted that it only
occurs after a clean install. If it is installed over a previous version(e.g.
EMX version) it installs and works correctly. A difference in the install over a
clean install and an overwrite is that the clean install ends without showing
the screen requesting a reboot.

A very minor further point on the overwrite install is that when the request for
reboot shows and you answer yes, it does not reboot, it kills current programs
but remains on the main OS/2 WPS screen, A manual reboot is required.
A further change has taken place on current nightlies(OS/2 3rd May) - the
installer version no longer works even if it is installed over the EMX Warpzilla
nightly. When trying to run installer version the following error message is
received in a window :-

XML Parsing Error: undefined entity
Location: chrome://navigator/content/navigator.xul
Line Number 63,Column 1:

 <window id="main-window"
 ^

   <broadcaster id="Communicator:Workmode"
 --^
Success! The OS/2 installer version installs as a clean install!! and runs

However although useable still getting error messages -

If the HELP > ABOUT is selected I get:-

XML Parsing Error: undefined entity
Location: jar:resource:///chrome/toolkit.jar!/content/global/about.xhtml
Line Number 84, Column 1:

   <a href="&vendorURL;">

When I go to MAIL NEWSGROUPS the message body window displays:-

XML Parsing Error: undefined entity
Location: jar:resource:///chrome/messenger.jar!/content/messenger/start.xhtml
Line Number 54, Column 10:

  <title>&startpage.title;</title>
---------^

But if an individual message is selected it displays correctly in the message
window.

BTW I really DON'T like the new scroll bars!!!
Mike Hitchcock, I have no idea what you are talking about. There haven't been
any changes to the installer in months AFAICS.
All the (changing) error messages that you post seem to indicate to me that you
should clean out your profile, there are many FAQs on the web that tell you how.
Severity: critical → normal
To start with I haope you understand that I am reporting ont the OS/2 version of
Mozilla downloaded from the /CONTRIB nightly sub directory which has been
updated to new versions almost on a daily basis.

As your comment regarding cleaning up my profile, even with entirely clean
intall(i.e. crate new) without any previous /mozilla profile files
existing(zipped and originals deleted and no config references to MOZILLAHOME
directory, so I have NO EXISTING PROFILE I get

XML Parsing Error: undefined entity
Location: chrome://communicator/content/profile/profileSelection.zul?manage=true
Line Number 53, column 1:

<dialog
^

I repeat that even with my profile files in position, the current EMX OS/2
nightly the last OS/2 release versions work fine, it is only the nightly
installer version is giving errors.

Just one further point - When running the installer into a clean directory, it
does not seem to complete, just stops before it gets to the screen asking
whether you want to reboot the computer, no error message it give the impression
that it has completed normally.
Success!!!

The Last three nightly of the Warpzilla Installer OS/2 versions now install,
load and run perfectly.

On the first drop of the three, Java(1.42) did not seem to work but it too now
runs fine. even on my dialup connection it seems fast and page load is quite
impressive, certainly faster than my winxp version or the OS/2 EMX version.
Hmm, should Mike's checkin to langenus.jst on the 24th of May have changed the
behavior for this bug (that I still neither understand nor can reproduce)? The
installer itself still wasn't changed a bit since your last post...

And actually,
http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/contrib/latest-trunk/mozilla-os2-installer.exe
is the same code (once it is installed) as
http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/contrib/latest-trunk/mozilla-i386-pc-os2-emx.zip
so it just cannot be faster.

But if you are happy, please resolve as WORKSFORME (you can reopen later if it
gets bad again).
My wager is that this was caused by the missing chrome registration for
brand.properties that was checked in.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.