Closed Bug 295411 Opened 20 years ago Closed 20 years ago

Mozilla Firefox 1.0.4 will not load

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: xaa, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; FDM)
Build Identifier: 

WinXP home. 

Worked fine up to 1.0.3 for me. 

Installed 1.0.4, browser would not run. Click shortcut, nothing happens. 
Taskmanager shows firefox.exe running. Click shorcut again, firefox.exe doubles 
in size in Taskmanager, still no window opens. Click shortcut again, size 
increases again, still does not run. Aborted process, ran in safe-mode - same 
effect. 

Uninstalled 1.0.4 using uninstaller located in firefox directory.  Re-installed 
1.0.3. Browser now runs, but any window.open command in javascript causes the 
browser to hang, and thereafter previous problem repeats. 

Browser is now non-functional, I am forced to return to IE to use the corporate 
webpages I normally visit. This is unsatisfactory.

Reproducible: Always

Steps to Reproduce:
1.Install Firefox 1.0.4
2.Click shortcut on desktop or start menu.


Actual Results:  
Nothing happens.

Expected Results:  
Program should start.
Sorry but FF1.0.4 works for many thousdand people and there must be something
wrong in your profile and or installation.

Please ask in the mozillazine.org Forums for help.

-> wfm
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
btw: 
I would suggest that you first uninstall 1.0.3, delete the whole Fiurefox
application folder except the plugins subfolder and reinstall 1.0.4
If that still doesn't work run "firefox -profilemanager" and create a new profile.

"Works for me" is not a viable resolution to the problem.  It does nothing to 
resolve the problem, you just simply say "hey, it works for me" and ignore the 
problem.  This is not acceptable.  I already knew it works for 58 million 
people, but it has STOPPED working for me.  The question is "Why?"

I have attempted to apply your solution, and have deleted the entire firefox 
folder except for plugins.  I then re-installed 1.0.4.  Please observe the 
screenshot, below:

http://img274.echo.cx/img274/1070/image016el.jpg

Please notice that Task Manager shows firefox.exe running, but no window opens.

If this bug was "hey, I click this button on the toolbar here and bad things 
happen", you wouldresolve it by saying "hey, it works for me."  Bugs are not 
resolved by saying "hey, it works for me," bugs are resolved by 
saying "hmmm...  Why doesn't it work for him?"
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Correction to previous post:

> If this bug was "hey, I click this button on the toolbar here and bad things 
> happen", you would NOT resolve it by saying "hey, it works for me."  
> Bugs are not resolved by saying "hey, it works for me," bugs are resolved by 
> saying "hmmm...  Why doesn't it work for him?"




Jim - did you "Visit the mozilla.org support page" before filing?
http://www.mozilla.org/support/

I suspect you can get an answer as to why it isn't working in a much shorter
time frame by posting in the Support forums which is linked from that page about
your problem.
http://www.mozilla.org/support/#forums
(In reply to comment #5)
> Jim - did you "Visit the mozilla.org support page" before filing?

Yes.  Here is what they say:

"If you encounter strange problems relating to bookmarks, downloads, window 
placement, toolbars, history, or other settings, it is recommended that you try 
creating a new profile and attempting to reproduce the problem before filing 
bugs. To create a new profile, see the Manage Profiles How-To. Migrate your 
settings files (Bookmarks, Saved Passwords, etc) over one by one, checking each 
time to see if the problems resurface. If you do find a particular profile data 
file is causing a problem, file a bug and attach the file."

However, their solution (rebuilding profile) did nothing, therefore I have no 
faulty profile to send.  The problem still exists in 1.0.4 for me.  And, 
judging by the most recent posts to Mozillazine, I'm not alone.  Here's just 
one thread for your perusal:

http://forums.mozillazine.org/viewtopic.php?t=270506

And judging by posts to other forums around the web, apparently, several people 
are having the same problem I am, as well as problems with 1.0.4 refusing to 
shut down, which may be a related problem.

http://forums.mozillazine.org/viewtopic.php?
t=270656&sid=cc324af952ecc20b8990298864abe9e7

Something else is happening, but I don't know what.  The same problem happens 
in "Safe Mode" so it's not an error with plugins or extensions, it has to be an 
incompatiblity somewhere with WinXP Home (which seems to be a common element) 
and FireFox 1.0.4.  

And please, let's not have anyone else say "hey, works for me!"  Going back to 
IE is NOT an option.  



WFM is a valid resolution when it does in fact WFM. Using the steps to reproduce
it does WFM and for the vast majority of users and without anything else to go
on there is little anyone can do to resolve this issue for you. You have also
reported one problem with 1.0.4 and a different problem with 1.0.3 which would
also makes it difficult to work on this bug even if there were reproducable
steps provided.

The one thread you provided for my perusal appears to be about someone's
firewall not being configured to allow access. I have my firewall set to prompt
when a program tries to access the net and this does WFM. If the user of the
firewall configures it not to prompt or has installed a firewall that doesn't
prompt IMO that is a problem that can barely be considered a Firefox problem and
is better handled by configuring the firewall to prompt or use a firewall that
prompts. There is also bug 270084 to add text to remind users to configure their
firewall during install.

The second thread appears to be about connections being held open and quite
possibly due to an extension or another program launched via Firefox.

Both posts don't describe the behavior you provided in comment #0. Did you ask
about your problem in the support forums and if so can you provide a link?
(In reply to comment #7)
> WFM is a valid resolution when it does in fact WFM.

Well, then there we are.  If "Works for Me" is a valid solution, then we're 
done.  I have disabled the firewall, I have created a new profile, I have 
deleted all themes and extensions, and I have run the program in 'safe mode'.  
The program still does not run - it appears in Task Manager, but no window 
opens.  But, since it works for everyone else, then we're done.  I thank you 
for your attention to my problem.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
If you are able to provide steps to reproduce please do open a new bug with the
steps. Also, a link to your post would be appreciated since these sort of system
specific problems are usually figured out outside of bugzilla.
(In reply to comment #9)
> If you are able to provide steps to reproduce please do open a new bug with 
the steps.

Unfortunately, the steps are as listed in my original note, above.  Install, 
click shortcut, nothing happens.  This is in safe-mode with a clean install and 
no themes or plugins.  Thus, there's no real point to starting a new bug - it 
will, by definition, just get an immediate "Works for Me" resolution.

> Also, a link to your post would be appreciated since these sort of system
> specific problems are usually figured out outside of bugzilla.

Unfortunately, there is little point to that, either.  Foolishly, since I 
actually LIKE Firefox, I grew upset at it's sudden failure and posted to two 
different threads on Mozillazine.  Now, I have been warned by a moderator and 
am publicly known as a Bad Person(tm), so there's no real point in continuing 
there.  

All I can do is wait until the number of people who have this bug grows, and 
hope that some of them are more computer-savvy than I and can actually provide 
enough useful data for it to be fixed.  I don't know why it doesn't work for 
me, and I don't know enough about how WinXP works to even hazard an intelligent 
guess.  I only know that of all the people who have reported problems with 
upgrading from 1.0.3 to 1.0.4, all of them have been on WinXP.  That's all I 
can tell you that's of any real use.  I simply don't know why Firefox won't 
load.  I only know I click the button, even in safe mode after deleting the 
entire directory, fresh install, new profile, no extensions, no themes...  It 
doesn't run.  It shows up on task manager, but no window opens.  And that's all 
I could post to a new bug, and the first response would be for someone to 
say "Works for me" and close it.  No real point to opening a new bug.  All I 
can do is wait until the number of people who have this bug grows, and hope 
that some of them are more computer-savvy than I and can actually provide 
enough useful data for it to be fixed.  

Until then, it looks like I'm back to (shudder) Internet Explorer for a few 
months.  Hopefully, it won't be for too long.


Well, warning or not - reading the thread could provide insight as to why this
is happening to you and from what I can tell by the threads you have provided no
one else. Even threads from other people that are experiencing the same issue
you described in comment #0 may shed light on the problem since so far it
appears you are the only one experiencing the problem as you described.

BTW: I wouldn't be surprised if a different program that is running is causing
this issue for you since creating a new profile w/o extensions or themes and
re-installing 1.0.4 cleanly didn't resolve this for you. It could also
potentially be a plugin but I doubt that. What ever the case this sort of
problem is best handled in the forums since from what has been provided so far
it is clearly system specific and there is no reliable way for anyone but
yourself to reproduce it.
You need to log in before you can comment on or make changes to this bug.