1653226 - FF 78 crash noting xml node toolbarbutton with id UITourTooltipClose

Status: RESOLVED FIXED

(Core :: XML, defect)

Description

[Peter Möller]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

updating firefox
starting firefox

Environment:
openSUSE leap 15.1 (others report it also for 15.2)

zypper dataset:
Repository : Mozilla
Name : MozillaFirefox
Version : 78.0.2-lp151.5.1
Arch : x86_64
Anbieter : obs://build.opensuse.org/mozilla
Installierte Größe : 198,5 MiB
Installiert : Ja
Status : aktuell
Quellpaket : MozillaFirefox-78.0.2-lp151.5.1.src
Zusammenfassung : Mozilla Firefox Web Browser

Actual results:

firefox just displays a white page with an error message, concerning toolbarbutton with id UITourTooltipClose
No further actions are possible beyond close

Expected results:

normal start of firefox

Comment 1

[Peter Möller]

there are perhaps some additional infos in the German suse forum:
https://forums.opensuse.org/showthread.php/541492-Firefox-78-startet-nicht?p=2945953#post2945953

the exact message of ff is:
<toolbarbutton id="UITourTooltipClose" class="close-icon"---------------"

The bug is pretty nasty, because no one may use its default profile anymore. So I would recommend a high priority error.

If you create a new profile, then ff starts as expected

Comment 2

[Peter Möller]

just recognised, that there is a bug report already. Could not find it, because the tagname is described only in the screenshot instead of the title ;-)
So call it a dup of #1174184

Comment 3

[bugs.mozilla.07.2020]

I can confirm this bug. i am running openSuSE Tumbleweed and did do updates this morning.
After a restart, I can only see "<toolbarbutton id="UITourTooltipClose" class="close-icon"" inside firefox.

How is the bug #1174184 related? Seems very different for me.

Comment 4

[bugs.mozilla.07.2020]

Firefox is back to normal after renaming/deleting addonStartup.json.lz4 .

The opensuse Bug https://bugzilla.opensuse.org/show_bug.cgi?id=1174184 is a duplicate.

Comment 5

[Daniel Bodea [:danibodea]]

I have set this component since it appears to be related to XML. Please set e more appropriate component is this one is incorrect.
I cannot confirm this bug since I haven't reproduced it but comment 3 states confirmation.

bugs.mozilla.07.2020, Peter Möller:

1. Can you give more detailed steps to reproduce for this crash?
2. Can you give us the crash reports in question? (you may find them in the profile they happened, in the "about:crashes" page)
   Thank you for your contribution!

Comment 6

[Peter Möller]

I really did nothing else. But here some hints, how I was able to solve it:
I used the solution to copy my profile to a win10 installation, open firefox, close it and copy back this profile to opensuse.
This worked so far. Just noted, i found a modified addonStartup.json.lz4.

Since I'm not sure, whether there are private datas in that file, I will not yet add those as attachment ;-)

Comment 7

[u655671]

I confirm this, seen on six PC with openSUSE 15.1 + FF up to date (https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.1)
Work around :

• for the two firsts juste apply the new update, works fine now
• for the 4 others, I need to create a new profile. Works fine now
• I found to late the solution with the deleting of addonStartup.json.lz4 so I can't confirm.

Feel free to ask me more information if needed.

Comment 8

[u655671]

On a seventh PC, deleting addonStartup.json.lz4 works

Comment 9

[Peter Möller]

Maybe I have the first case, where deleting addonStartup.json.lz4 didn't help (on Tumbleweed), I will report on Friday, since my instructions were done by phone and on Friday I will see the PC myself and the actions being done ;-).

Comment 10

[Peter Möller]

My feedback was missing. I really have the first Laptop (tumbleweed), where both strategies failed:

• it did not help to rename addonStartup.json.lz4.
• it did not help to open FF in Win10 and copy back the moziila directory.

I don't know the reason. Is there any suggestion, what should be analysed? Or is the reason well known meanwhile?

Comment 11

[Guo Yunhe]

I also see this error. Not first time. Last year or two years ago, I noticed same error after openSUSE Tumbleweed update.

Simple solution is to run firefox --safe-mode and click Refresh Firefox.

Comment 12

[Guo Yunhe]

Attachment: XML error after update in openSUSE Tumbleweed

Comment 13

[1261043829]

(In reply to Guo Yunhe from comment #11)

I also see this error. Not first time. Last year or two years ago, I noticed same error after openSUSE Tumbleweed update.

Simple solution is to run firefox --safe-mode and click Refresh Firefox.

Thinks.This command have solved mu problem. My firefox version is 82 and host on opensuse tumbleweed.

Comment 14

[jay]

The root of the bug seems to be clearly described in this comment on openSUSE's Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1174184#c21

Easy fix for me by deleting addonStartup.json.lz4 from all Firefox profiles. These are in ~/.mozilla/firefox/[profile_name]/addonStartup.json.lz4 on SUSE.

Comment 15

[Peter Möller]

@jay: Its good to know, that it helped, but it doesn't always. see also comment 10

Comment 16

[Peter Möller]

I don't see any sense in this one. Yes, it had been a problem along with moving from a specific version to newer versions. I'm willing to close it, if there will be no more responses

Comment 17

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 18

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:peterv, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 19

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Going to close this per comment 16.
Thank you for reporting this and getting back, dear reporter.