Talk:Browser will not start up: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
 
(6 intermediate revisions by 2 users not shown)
Line 16: Line 16:
=="The program must close to allow a previous installation attempt to complete. Please restart." on Vista==
=="The program must close to allow a previous installation attempt to complete. Please restart." on Vista==
This is [https://bugzilla.mozilla.org/show_bug.cgi?id=369221 bug 369221], Vista only, fixed on trunk and possibly will be fixed in 2.0.0.5. The same message was given in [https://bugzilla.mozilla.org/show_bug.cgi?id=283680 bug 283680], all Windows, fixed in 1.0.1. Since 1.0.1 is a long time ago, I'm dropping references to that fix.--[[User:Np|Np]] 17:52, 18 May 2007 (UTC)
This is [https://bugzilla.mozilla.org/show_bug.cgi?id=369221 bug 369221], Vista only, fixed on trunk and possibly will be fixed in 2.0.0.5. The same message was given in [https://bugzilla.mozilla.org/show_bug.cgi?id=283680 bug 283680], all Windows, fixed in 1.0.1. Since 1.0.1 is a long time ago, I'm dropping references to that fix.--[[User:Np|Np]] 17:52, 18 May 2007 (UTC)
:The Firefox  bug fixed in 1.0.1 is [https://bugzilla.mozilla.org/show_bug.cgi?id=283680 bug 283680]. [https://bugzilla.mozilla.org/show_bug.cgi?id=369221 Bug 369221] refers to the ""Error opening file for writing..."error, as shown in [https://bugzilla.mozilla.org/attachment.cgi?id=253888 this screenshot] which was attached to the bug report. Also, "The program must close to allow a previous installation attempt to complete. Please restart." error on Vista is related to this NEW bug, (spun off from [https://bugzilla.mozilla.org/show_bug.cgi?id=369937 bug 369937] which was referenced in the   [http://kb.mozillazine.org/index.php?title=Browser_will_not_start_up&diff=31806&oldid=31080 part you edited out] of this section, [https://bugzilla.mozilla.org/show_bug.cgi?id=370219 Bug 370219 – add xpicleanup.dat to removed-files.in on trunk and MOZILLA_1_8_BRANCH]From bug 370219:
:The Firefox  bug fixed in 1.0.1 is [https://bugzilla.mozilla.org/show_bug.cgi?id=283680 bug 283680] I fixed your link. [[User:Alice Wyman|Alice]] 11:05, 20 May 2007 (UTC)
:{| {{prettytable}}
 
==Faulty installation==
The article mentions "JS_DHashTableOperate could not be located in the dynamic link library js3250.dll" is cased by a faulty install, could a bad install also cause this:
http://forums.mozillazine.org/viewtopic.php?t=562786
 
"The procedure entry point ?ListenerDied@nsCategoryObserver@@QAEXXZ could not be located in the dynamic link library xpcom_core.dll"
 
If so, perhaps we should rename that section to something less specific.--[[User:Lethargy|name already taken]] 06:50, 1 July 2007 (UTC)
 
:If the solution to the  xpcom_core.dll error you referenced also turns out to be a clean reinstall of Firefox using an official installer (which is the last step in the [[Standard diagnostic - Firefox |standard diagnostic]] advice given in the forum thread)  then I think we should add a new section and maybe mention specific startup errors that point to a faulty installationIn any case, I think that the current JS_DHashTableOperate section should be removed since the underlying bug appears resolved (see below).  [[User:Alice Wyman|Alice]] 16:54, 1 July 2007 (UTC)
 
==JS_DHashTableOperate section==
Here is what that section now says:
{| {{prettytable}}
|-
|-
|[https://bugzilla.mozilla.org/show_bug.cgi?id=370219#c1 bug 370219 comment 1 (2007-02-12) by Seth Spitzer]<br><br>  
|'''"JS_DHashTableOperate could not be located in the dynamic link library js3250.dll"'''<br><br>If you attempt to start Firefox 2.0.0.0 and receive the error, "The procedure entry point JS_DHashTableOperate could not be located in the dynamic link library js3250.dll", it indicates a faulty installation caused by upgrading from an earlier Firefox version without exiting all firefox.exe processes. Uninstall Firefox and install the latest version from [http://mozilla.com Mozilla.com].[https://bugzilla.mozilla.org/show_bug.cgi?id=357890]
as robert indicated, when we do an install or when software update runs, if we detect this file, we could (and should) remove it, to help reduce issues like those reported in the forums such as:<br>
http://forums.mozillazine.org/viewtopic.php?p=2736957 and<br>
http://forums.mozillazine.org/viewtopic.php?p=2737780<br>
<snip><br>
note, this would be trunk and 1.8 branch only, and not the 1.8.0 branch, where
we still use the xpinstaller.<br>
<snip>
|-  
|-  
|}
|}
:In any case, since bug 369921 is' ''fixed on trunk and possibly will be fixed in 2.0.0.5'' but not fixed in the current or the upcoming  2.0.0.4 release, I think we should add back the fix you removed from this section. OK? [[User:Alice Wyman|Alice]] 11:05, 20 May 2007 (UTC)
I reviewed the bug report, https://bugzilla.mozilla.org/show_bug.cgi?id=357890 and in it,  on 2007-01-12, Robert Strong stated in [https://bugzilla.mozilla.org/show_bug.cgi?id=357890#c17 comment 17], ''I believe this was fixed by [https://bugzilla.mozilla.org/show_bug.cgi?id=357922 bug 357922] as comment #13 ... resolving -> wfm''.  If you look at [https://bugzilla.mozilla.org/show_bug.cgi?id=357890#c13 comment 13], 2006-12-15, Daniel Veditz  said, ''I'm pretty sure this will turn out to be a dupe of the bug on the installer not making sure Firefox is fully gone.''  Based on that, I'd like to remove the section altogether, if no one objects, since  the underlying [https://bugzilla.mozilla.org/show_bug.cgi?id=357922 Firefox 2.0.0.0 installer bug] is fixed in Firefox 2.0.0.1 and later. [[User:Alice Wyman|Alice]] 16:54, 1 July 2007 (UTC)
 
Section removed. [[User:Alice Wyman|Alice]] 16:58, 10 July 2007 (UTC)

Latest revision as of 16:58, 10 July 2007

Do not ask questions here. Try the MozillaZine Forums instead.

FYI, in FF 1.0.3, when in safe mode, one can't disable extensions; one can only delete them - 'Disable' is itself disabled. (I find that, anyway; the Options button is greyed out (and 'Disable' is grey in the right-mouse menu), but Uninstall and Update are available.) My guess: if this is a new bug, a bug needs filing/fixing, if it's an old bug, the dox need changing.

Mozilla Suite (Windows) fails to start

I added this section because the problem is still being posted to the forums, for example, Mozilla 1.7.8 won't start (Posted: Wed 6th Jul 2005) and Mozilla won't open! (Posted: Tue 15th Mar 2005). Alice 16:27, 17 September 2005 (PDT)

Windows-specific problems - Windows Vista

On Vista, the Start -> "Run" box is not shown by default. You can use the "Start Search" box instead. See http://blogs.msdn.com/tims/archive/2006/09/18/windows-vista-secret-3-bringing-back-start-run.aspx and http://www.computerperformance.co.uk/vista/vista_run_command.htm

...Apparently Start -> Start search -> %appdata% does work. It's mentioned here as working on Vista. See also http://www.mozilla.org/support/firefox/profile#appdata Alice 18:44, 2 March 2007 (UTC)

"The program must close to allow a previous installation attempt to complete. Please restart." on Vista

This is bug 369221, Vista only, fixed on trunk and possibly will be fixed in 2.0.0.5. The same message was given in bug 283680, all Windows, fixed in 1.0.1. Since 1.0.1 is a long time ago, I'm dropping references to that fix.--Np 17:52, 18 May 2007 (UTC)

The Firefox bug fixed in 1.0.1 is bug 283680 I fixed your link. Alice 11:05, 20 May 2007 (UTC)

Faulty installation

The article mentions "JS_DHashTableOperate could not be located in the dynamic link library js3250.dll" is cased by a faulty install, could a bad install also cause this: http://forums.mozillazine.org/viewtopic.php?t=562786

"The procedure entry point ?ListenerDied@nsCategoryObserver@@QAEXXZ could not be located in the dynamic link library xpcom_core.dll"

If so, perhaps we should rename that section to something less specific.--name already taken 06:50, 1 July 2007 (UTC)

If the solution to the xpcom_core.dll error you referenced also turns out to be a clean reinstall of Firefox using an official installer (which is the last step in the standard diagnostic advice given in the forum thread) then I think we should add a new section and maybe mention specific startup errors that point to a faulty installation. In any case, I think that the current JS_DHashTableOperate section should be removed since the underlying bug appears resolved (see below). Alice 16:54, 1 July 2007 (UTC)

JS_DHashTableOperate section

Here is what that section now says:

"JS_DHashTableOperate could not be located in the dynamic link library js3250.dll"

If you attempt to start Firefox 2.0.0.0 and receive the error, "The procedure entry point JS_DHashTableOperate could not be located in the dynamic link library js3250.dll", it indicates a faulty installation caused by upgrading from an earlier Firefox version without exiting all firefox.exe processes. Uninstall Firefox and install the latest version from Mozilla.com.[1]

I reviewed the bug report, https://bugzilla.mozilla.org/show_bug.cgi?id=357890 and in it, on 2007-01-12, Robert Strong stated in comment 17, I believe this was fixed by bug 357922 as comment #13 ... resolving -> wfm. If you look at comment 13, 2006-12-15, Daniel Veditz said, I'm pretty sure this will turn out to be a dupe of the bug on the installer not making sure Firefox is fully gone. Based on that, I'd like to remove the section altogether, if no one objects, since the underlying Firefox 2.0.0.0 installer bug is fixed in Firefox 2.0.0.1 and later. Alice 16:54, 1 July 2007 (UTC)

Section removed. Alice 16:58, 10 July 2007 (UTC)