264362 - Error launching browser window:no XBL binding for browser, browser doesn't open.

Status: RESOLVED WORKSFORME

(Firefox :: Installer, defect)

Description

[austin zaletel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910

Installed Firefox Version 1.0 PR and several themed extensions (Noia, Doodle)
via the automatic update in the Firefox Preferences.  Upon restart, received
message, "Error launching browser window:no XBL binding for browser"  and
browser fails to load.  

Reproducible: Always
Steps to Reproduce:
1. Uninstalled and Reinstalled 1.0 PR with same results
2. Installed nightly builds from around Oct 2 to present with same results
3. Installed and currently running Mozilla 1.7.3 with no problems
Actual Results:  
Nothing.  Upon uninstall received a message stating that all files have not been
removed during this uninstall, and asked if I wanted to delete forlder, and said
yes (I don't know if this is relevent).  This made no improvement in launching
browser after reinstall.  Mozilla 1.7.3 runs with no problems.

Expected Results:  
Opened properly and displayed browser window.

I had several themes installed, Noia extreme, doodle classic, and the weatherbug
extension.  All worked fine in the previous version.  No theme loads, however,
upon launching browser.  In fact, nothing loads except error message and blank
window.  After uninstall (which would presumable get rid of themes) same problem
occurs.

Comment 1

[dolphinling]

In your profile directory, find a file called xul.mfl or xul.msafl and delete
it. That should fix the problem.

If it does, mark this as worksforme.

Comment 2

[austin zaletel]

Tried to find xul files but nothing appeared with the names xul.mfl or xul.msafl
 in the firefox directory.  In the mozilla directory there were files with xul
in the name (ex: tab.xul or dom_xul.xpt) but not xul.mfl or xul.msafl  .  

Comment 3

[austin zaletel]

Found proper profile folder (previously hidden) and worked for me.  Bug
resolved.    Thanks for the help.