Bug 1077590 - FF 58 XML Parsing Error in browser.xul
FF 58 XML Parsing Error in browser.xul
Status: RESOLVED WORKSFORME
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Firefox
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-25 11:00 UTC by Michael Woski
Modified: 2018-03-07 07:58 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Woski 2018-01-25 11:00:49 UTC
since I installed FF58 I get the following error.

XML Parsing Error: undefined entity
Location: chrome://browser/content/browser.xul
Line Number 245, Column 5:    <broadcaster id="viewTabsSidebar" autoCheck="false" sidebartitle="&syncedTabs.sidebar.label;"


After a fresh installation the browser initially starts normally for each user on the system. But from the second start on FF stops working with above error message.

I have deleted the complete .mozilla folder, but to no avail.

Safe-mode works. The cleaning function in safe-mode does not solve the issue though.

Rolling back to FF57 everything runs smoothly again.
Comment 1 Wolfgang Rosenauer 2018-01-25 12:44:05 UTC
Are you running under KDE or another desktop environment?
Comment 2 Wolfgang Rosenauer 2018-01-25 15:03:31 UTC
Which extensions are installed?
Comment 3 Michael Woski 2018-01-25 15:06:24 UTC
(In reply to Wolfgang Rosenauer from comment #2)
> Which extensions are installed?

Hi Wolfgang,

I'm running under KDE (from KDE:Unstable).

There are no (user) extensions installed (I deleted the .mozilla folder).

bye Michi
Comment 4 Wolfgang Rosenauer 2018-01-25 15:27:40 UTC
Hmm, this happened before at some point but the usual reason is not the problem here.
We are patching browser.xul for KDE and if the KDE version is out of sync we run into something like this. But I verified this and this does not seem to be the case here.
I'm wondering if it affects everyone running under KDE but this is the first report I've seen anywhere.
Comment 5 Wolfgang Rosenauer 2018-01-29 21:59:21 UTC
I might have found something causing this.
Which UI language uses your Firefox typically?

Also I'm just uploading FF 58.0.1 to mozilla. You can try that one and see how it behaves.
Comment 6 Michael Woski 2018-01-30 00:14:25 UTC
(In reply to Wolfgang Rosenauer from comment #5)
> I might have found something causing this.
> Which UI language uses your Firefox typically?
> 
> Also I'm just uploading FF 58.0.1 to mozilla. You can try that one and see
> how it behaves.

english
Comment 7 Michael Woski 2018-01-30 15:47:39 UTC
> Also I'm just uploading FF 58.0.1 to mozilla. You can try that one and see
> how it behaves.

same problem remains :-(
Comment 8 Michael Woski 2018-02-11 13:29:46 UTC
I had to do a fresh installation of my system and the issue vanished
Comment 9 Wolfgang Rosenauer 2018-03-07 07:58:53 UTC
thanks for confirming