This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Thunderbird 78.5.0 does not start : Parser error

  • 3 antwoorde
  • 1 het hierdie probleem
  • 14 views
  • Laaste antwoord deur sfhowes

more options

I updated to 78.5.0. And now Thunderbird doen not start at all. I get an tiny grey window telling : Parser error : XML-parsefout: ongedefinieerde entiteit Locatie: chrome://messenger/content/messenger.xhtml Regelnummer 901, kolom 3:

 <key id="openLightningKey"
</pre>

--^ "

and I have no file "messenger.xhtml" in thunderbird Chrome, in fact the whole messenger map is not there. So I cant remove line 901 either.

Who understands what went wrong ? and what to do Thanks Ferdinand

I updated to 78.5.0. And now Thunderbird doen not start at all. I get an tiny grey window telling : Parser error : XML-parsefout: ongedefinieerde entiteit Locatie: chrome://messenger/content/messenger.xhtml Regelnummer 901, kolom 3: <key id="openLightningKey" --^ " and I have no file "messenger.xhtml" in thunderbird Chrome, in fact the whole messenger map is not there. So I cant remove line 901 either. Who understands what went wrong ? and what to do Thanks Ferdinand

Gewysig op deur Dieten

All Replies (3)

more options
more options

As I can't start I cant apply the solution you proposed for the other case.

more options

Open the profile folder, which is located by default in:

C:\Users\username\AppData\Roaming\Thunderbird\Profiles\randomstring.default

AppData is hidden by default.

Open prefs.js in a text editor, look for the line

user_pref("gfx.direct2d.disabled", false);

change false to true, save the change, then start TB (if you can).