Beginning on October 25th, 2016, Persona will no longer be an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 293263 - Preferences menu produces XML parsing error
: Preferences menu produces XML parsing error
Product: SeaMonkey
Classification: Client Software
Component: General (show other bugs)
: 1.7 Branch
: x86 Linux
: -- major (vote)
: ---
Assigned To: general
Depends on:
  Show dependency treegraph
Reported: 2005-05-07 08:01 PDT by Timothy Miller
Modified: 2005-10-13 10:28 PDT (History)
0 users
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description Timothy Miller 2005-05-07 08:01:02 PDT
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050504
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050504

I just upgraded from 1.7.5 to 1.7.7.  When I try to open the "Preferences..."
menu, I get a Gecko error.  You guys also need to make it so I can copy and
paste it, but here it is:

XML Parsing Error: not well-formed
Location: chrome://communicator/content/pref/pref.xul
Line Number 1, Column 10:

" align="start"?

Reproducible: Always

Steps to Reproduce:
1. Edit menu
2. Preferences...

Actual Results:  

Expected Results:  
Preferenes menu

Gentoo ebuild
Comment 1 Ben Fowler 2005-05-07 10:09:58 PDT
You are probably in the wrong place for troubleshooting a Gentoo ebuild.

I would suspect that your chrome is messed up, and I agree that these problems
are hard to diagnose, see Bug 286252 "After new nightly install minimal error 
window on warpzilla load" for another example.

You might want to try with a completely fresh profile and check the permissions
on ~/.mozilla .
Comment 2 Gervase Markham [:gerv] 2005-09-27 01:56:36 PDT
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Comment 3 Gervase Markham [:gerv] 2005-10-13 10:28:06 PDT
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Note You need to log in before you can comment on or make changes to this bug.