xml error when adding bookmark

Bug #16936 reported by evan
32
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Fix Released
Medium
Ian Jackson

Bug Description

I opened firefox.
I went to the website www.google.com.
I selected "Bookmark This Page" in the menu "Bookmarks".
Firefox showed me this xml error:

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

hildren>
^
----

I use hoary with firefox version 1.0.2-0ubuntu5.1 (upgraded today 12 may 2005).

Revision history for this message
Daniel Robitaille (robitaille) wrote :

I cannot reproduce that bug on my machine (i386 Hoary, also using
1.0.2-0ubuntu5.1). But one other person on IRC tonight has said to have
experienced this bug as well, so obviously it is occuring for some users.

Revision history for this message
Thom May (thombot) wrote :

please try quitting firefox, removing ~/.mozilla/firefox/*/XUL.mfasl; and
restarting firefox again.

Revision history for this message
evan (evan-monroig) wrote :

(In reply to comment #2)
It did remove the problem.

by the way, it occured just after upgrading to the new version today. I had not
changed anything on my system. Sorry if it was not a bug ;)

Revision history for this message
Thom May (thombot) wrote :

it is a bug; it'll be fixed in the next round of security releases. Thanks for
notifying us of this.

Revision history for this message
Thom May (thombot) wrote :

*** Bug 16951 has been marked as a duplicate of this bug. ***

Revision history for this message
Thom May (thombot) wrote :

*** Bug 16952 has been marked as a duplicate of this bug. ***

Revision history for this message
Forrest Humphrey (forrest-humphrey) wrote :

(In reply to comment #2)
> please try quitting firefox, removing ~/.mozilla/firefox/*/XUL.mfasl; and
> restarting firefox again.

I had same problem with firefox 1.0.6-0ubuntu0.1 in hoary. The above fixed it
perfectly.

Revision history for this message
Ian Jackson (ijackson) wrote :

I assume that this bug has been fixed now. If not then it's probably rather
late. If there are still problems worth looking at, please get back to me
(reopen or refile the bug).

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.