User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168pre) Gecko/20090812 Ubuntu/9.10 (karmic) Shiretoko/3.5.3pre Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:22.214.171.124pre) Gecko/20090812 Ubuntu/9.10 (karmic) Shiretoko/3.5.2 I run Firefox 3.5.2 (and 3.5.3pre) on Ubuntu Karmic alpha 3, with the following extensions installed : https://addons.mozilla.org/fr/firefox/collection/valeryan_24?sortby=name After installation of these extensions, I get an error on starting Firefox with this message : XML Parsing Error: undefined entity Location: chrome://browser/content/browser.xul Line Number 34, Column 1:<window id="main-window" ^ Nothing else is possible. This error happened many times, I have to completely remove Firefox, including extensions, bookmarks, profiles and folders to reinstall it. Sometimes also extensions are not able to install, they are downloaded but after restart do not appear in addons. Reproducible: Always Expected Results: Start normally...
Sounds like one of your extensions is not compatible; the extension has to be updated by the extension author to make it work with the latest Firefox version.
Version: unspecified → 3.5 Branch
I get the message on *all* xpi files on Mozilla Firefox 3.5.2, OpenSUSE 11.0. XML Parsing Error: undefined entity Location: chrome://mozapps/content/xpinstall/xpinstallConfirm.xul Line Number 26, Column 38: <description class="warning">&warningMain.label;</description> -------------------------------------^
Create a new profile, and install on of those addons. If one causes it, it will continue to show it.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
No response from Reporter -> INCOMPLETE
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.