Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Since upgrade to 78.3.2 get XML parsing error, have to load in safe mode

  • 5 replies
  • 1 has this problem
  • 2 views
  • Last reply by graham35

graham35
graham35

XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: 

 <key id="openLightningKey"
</pre>

I have a crash number of:
Crash ID: bp-8198e7d5-da18-4d2e-b61a-c41280201102

i have tried turning my attachments off to no avail.

Any assistance would be great as I've grown fond of using and was looking forward to new version.

I'm on Gnome 3.38.1  Pop! OS 20.10
XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: <key id="openLightningKey" I have a crash number of: '''Crash ID: bp-8198e7d5-da18-4d2e-b61a-c41280201102''' i have tried turning my attachments off to no avail. Any assistance would be great as I've grown fond of using and was looking forward to new version. I'm on Gnome 3.38.1 Pop! OS 20.10

Chosen solution

Another safe mode factor, hardware acceleration, probably won't help either, but a new profile might. Help/Troubleshooting, about:profiles, create a new profile, add an account, and see if the error disappears. If it does, data from the old profile can be copied to the new one. Either profile can be launched from about:profiles.

Read this answer in context 👍 1

All Replies (5)

sfhowes
sfhowes
  • Top 25 Contributor

Launch in safe mode, 'Reset toolbars & controls', 'Make changes & restart'. If that doesn't help, try to update to the latest version 78.4.3.

https://support.mozilla.org/en-US/questions/1313038

graham35
graham35 Question owner

Thanks for the help, it didn't fix the problem. Tried the safe-mode options but the same.

In desperation I removed and reinstalled - but I get the same error with a fresh install.

i can only get 78.3.2 for my Linux system 78.4.3 isn't available.

sfhowes
sfhowes
  • Top 25 Contributor

Chosen Solution

Another safe mode factor, hardware acceleration, probably won't help either, but a new profile might. Help/Troubleshooting, about:profiles, create a new profile, add an account, and see if the error disappears. If it does, data from the old profile can be copied to the new one. Either profile can be launched from about:profiles.

graham35
graham35 Question owner

This is the error i can see in Console:

2020-11-18 21:17:26 gloda.datastore ERROR got error in _asyncTrackerListener.handleError(): 19: constraint failed Log4moz.jsm:766 

   append resource:///modules/gloda/Log4moz.jsm:766
   log resource:///modules/gloda/Log4moz.jsm:416
   error resource:///modules/gloda/Log4moz.jsm:424
   handleError resource:///modules/gloda/GlodaDatastore.jsm:1916

in the Warnings I get this:


Lightning: Parsing failed for parts of the item (while this is considered to be a minor issue, we continue processing the item): BEGIN:VCALENDAR

VERSION:2.0

X-WR-CALNAME:Calendar

PRODID:-//The Horde Project//Horde iCalendar Library//EN

BEGIN:VTIMEZONE

TZID:Europe/London

graham35
graham35 Question owner

sfhowes.

I turned off the acceleration and it seemed to do the trick!