Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

opening Firefox displays xml parsing error

  • 8 ответов
  • 1 имеет эту проблему
  • 142 просмотра
  • Последний ответ от jon_joy_1999

more options

I'm using Firefox on a Samsung moto G6 with Android 9. When I open Firefox it displays a yellow page that says XML Parsing Error: no root element found. Location: chrome://geckoview/content/geckoview.xhtml line number 1, column 1.

I can't open any pages. I've tried restarting my device but I still get the message. What should I do?

Выбранное решение

Hi

I have looked into this one a bit further and have found that our developers are aware of this issue. You can follow progress on this work and add comments at:

https://bugzilla.mozilla.org/show_bug.cgi?id=1668842

Прочитайте этот ответ в контексте 👍 1

Все ответы (8)

more options

Hi

Do you have any add-ons installed in Firefox for Android?

more options

I don't believe I have any add-ons installed. When I go to Addons in Firefox I'm presented with a list of items, all with a + box.

Изменено jon_joy_1999

more options

What is the address of the website that you are trying to view?

more options

It was all websites. Google, Wikipedia, Slate, the Support button in the About menu for Firefox all gave me this error.

more options

Is this a version of Firefox for Android that you have installed from the Google Play store?

more options

Yes. I installed it a few months ago from Google Play store.

more options

Выбранное решение

Hi

I have looked into this one a bit further and have found that our developers are aware of this issue. You can follow progress on this work and add comments at:

https://bugzilla.mozilla.org/show_bug.cgi?id=1668842

more options

Thanks for the information Seburo. I just tested the browser again on that phone and the issue seems to have resolved itself. But if it happens again I'll use this to try to provide more information to bugzilla.