firefox-x11-devel 4.0b9_0 does not open the GUI

[cubranic@…]

After upgrading from @4.0b7_1+gnome+official_branding to 4.0b9+gnome+official_branding, running "firefox" just returns without opening a window or printing an error.

If I instead run "firefox -ProfileManager", I get the following error:

XML Parsing Error: undefined entity
Location: chrome://mozapps/content/profile/profileSelection.xul
Line Number 53, Column 1:

<dialog
^

This looks similar to ​https://qa.mandriva.com/show_bug.cgi?id=62105

[jeremyhu (Jeremy Huddleston Sequoia)]

Can you try moving aside your firefox profile just to eliminate that possibility (mv ~/.mozilla ~/.mozilla.bak) ... you can then move it back later.

[jeremyhu (Jeremy Huddleston Sequoia)]

Also similar to this issue I reported upstream which I saw on one install:

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

It went away with +internal_dependencies ... so if the profile moving doesn't work around it, can you give that variant a try.

[cubranic@…]

Moving the profile does not help, still the same thing happens: "firefox" with no arguments or "-safe-mode" returns to the shell prompt without opening a window or printing an error. Running with option "-ProfileManager" opens a plain window with the XML parsing error in "profileSelection.xul".

[cubranic@…]

Variant +internal_dependencies works for me too.

[cubranic@…]

The same issue is still present in @4.0b11_0+gnome+official_branding, and a workaround is to use @4.0b11_0+gnome+internal_dependencies+official_branding, which runs fine. (Except for #28040, which is a minor cosmetic issue.)

[jmroot (Joshua Root)]

Any change with 9.0_alpha20110820?

[cubranic@…]

Sorry, I stopped using the devel port of Firefox now that firefox-x11 is up-to-date with the current release of Firefox.