Geck XML Parsing Error when Opening Bookmark Manager




14 years ago
13 years ago


(Reporter: james.p.barrett, Unassigned)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050418 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050418 Firefox/1.0.3

If I try to Add a page to my bookmarks, or open "Manage Bookmarks" from the menu
up pops a Gecko window with the following error:

XML Parsing Error: syntax error
Location: chrome://bowser/content/bookmarks/addBookmark2.xul
Line Number 1, Column 1;

treecols anonid="treecols">

Reproducible: Always

Steps to Reproduce:
1.Bookmark this Page

Actual Results:  
A Gecko Error

Expected Results:  
Adding a bookmark
Do you get the same if you run Firefox in the safemode ?
(firefox -safe-mode)
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.