337369 - No XBL binding startup problem

Status: RESOLVED INVALID

(Toolkit :: Startup and Profile System, defect)

Description

[tiogshi]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060427 Debian/1.7.13-0ubuntu05.04
Build Identifier: Several versions; see comments.

I was using Firefox 1.0.5.2, installed from the Ubuntu package. When starting up, I would get the message box "Error starting browser window:no XBL binding for browser". On the console, I get the following...

*** Failed to load overlay chrome://singlewindow/content/singlewindow.xul
*** Failed to load overlay chrome://forecastfox/content/forecastfox.xul
*** Failed to load overlay chrome://downloadmgr/content/browserOverlay.xul

...before the window appears. After consulting BugZilla, I completely uninstalled, including configuration and extensions, and tried re-installing, and got errors in the package configuration.

Updating mozilla-firefox chrome registry..../update-mozilla-firefox-chrome: line 106:  5551 Segmentation fault      firefox-bin -register >/dev/null 2>&1
E: Registration process existed with status: 139
E: /usr/lib/mozilla-firefox/extensions/installed-extensions.txt still present. Registration might have gone wrong.
mv: cannot stat `/usr/lib/mozilla-firefox/defaults.ini': No such file or directory

I tried removing and then installing Firefox 1.0.8, with the same results. I am currently using Mozilla 1.7.13 to enter this, as Lynx doesn't like Bugzilla.

No extensions were installed in the last week; no updates were installed in the last week; the system has rebooted numerous times in that period. The bug started occuring after I installed the Mono framework, but I cannot see how or why this affects Firefox.

Reproducible: Always

Steps to Reproduce:
1. Try to start firefox.
Actual Results:  
Error messages and dialog as described.

Expected Results:  
Normal startup.

As best as I can see, installing MonoDevelop or libgecko-cil, both of which depend on mozilla-firefox, somehow breaks Firefox. They might, however, be completely unrelated.

Comment 1

[tiogshi]

Finally found a fix. Deleted my local configuration (after copying bookmarks and cookies out, obviously), and then re-installed completely. Works, and chrome registers properly. Lost extensions and plugins, but at least I have a non-Lynx webbrowser again.

On further reading of the log I posted, I am extremely confused, since I have not used the singlewindow or forecastfox plugins for some time. Worse, that still does not explain the errors when updating the chrome registry.

Comment 2

[Philip Withnall (unavailable)]

(In reply to comment #1)
> Finally found a fix. Deleted my local configuration (after copying bookmarks
> and cookies out, obviously), and then re-installed completely. Works, and
> chrome registers properly. Lost extensions and plugins, but at least I have a
> non-Lynx webbrowser again.
> 
> On further reading of the log I posted, I am extremely confused, since I have
> not used the singlewindow or forecastfox plugins for some time. Worse, that
> still does not explain the errors when updating the chrome registry.
> 

This sounds to me like something went wrong with the installation by apt-get, or there was some corruption.
Marking as INVALID.