Mozilla 1.7 RC1 won't start; 1.5 okay



14 years ago
13 years ago


(Reporter: Terry Carroll, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier:

I installed 1.7 RC1; it started okay.  I tried exiting and restarting, and it
won't start.  It's as if the icon isn't even being clicked.

Reinstalling 1.7 doesn't help.  When I go back to 1.5, Mozilla starts okay.

Rebooting did not help.

Reproducible: Always
Steps to Reproduce:
1. Install Mozilla 1.7RC1
2. Exit Mozilla
3. Attempt to start Mozilla

Actual Results:  

Expected Results:  
Mozilla should have started

No diagnostic messages of any kind.

Comment 1

14 years ago
Terry, do you have any extensions or third-party-themes installed?
Did you install cleanly or over an old installation?

Comment 2

14 years ago
And: Does this also happen with a new profile? (commandline: "mozilla

Comment 3

14 years ago
I have tested versions 1.5, 1.6a, 1.6b, 1.7, 1.8a under win32, in a XPpro SP1 
system and I have the following result :
1.5 to 1.6a start
1.6b to latest (1.8a)

It significate this is a change between 1.6a and 1.6b version which break 
starting of Mozilla under XP.

I have try latest firefox and it works fine, but because I am often under linux 
with mozilla I prefer this one...

If you want I try other version please send the link of the corresponding full 
installer and I will try the corresponding release...

Please correct soon this bug, this is a realy blocker bug which avoid to 
convert to openbrowser people...

Comment 4

14 years ago
same with 'mozilla -profilemanager'

same if I re-install (uninstall+install) or install over old version...

this seems to be a XP code related bug...

Have a good day

Comment 5

14 years ago
duplicate of bug 231869

Comment 6

14 years ago
Hi, this is the OP again.  I found I could get around this problem by following
the procedure set out here:

In particular, deleting the GRE directory.

The implication is that this may be a duplicate of bug 211694; however, if
that's the case, then something's wrong, because bug 211694 is marked as
resolved in a much earlier release.

Of course, it's resolved as a dupe of bug 195600, which in turn is resolved as
WORKSFORME.  WORKSFORME isn't really a resolution; it's just a statement that
the developer was able to do the same action without seeing the bug, and closed
it out without fixing anything.  It doesn't correct the bug and certainly
doesn't do anything for the user experiencing the bug.

Given that the GRE deletion fixes it, my guess is that the bug is best described
as "Mozilla won't start when a GRE file is left over from a previous release."

This is probably really two bugs: first, a deinstall of Mozilla should delete
the GRE; but second, if the GRE isn't deleted, a subsequent release shouldn't
fail because of the leftover spoor.  I don't know if this is best thought of as
an install bug (i.e., at installation, if spoor left over from a prior
installation is found, it should be deleted/overwritten) or an initialization
bug (if a bad GRE directory is found, Mozilla should at least present an error
message instead of silently terminating).

Just some thoughts.

Comment 7

14 years ago
Still valid in Mozilla 1.7 RC1

I have try the solution, and remove all the GRE directory (in registry or in
FileSystem) and still mozilla does not start anymore...

Is their a way to show aa backtrace as it's possible under linux???

The solution ou give us don't solve anythink...

Please change this bug as NEW and BLOCKER!!!

Comment 8

14 years ago
Rapsys, it sounds like your bug is a different one from the one I reported.

Comment 9

14 years ago
Please change this bug as WON'T FIX and I will post a new bug report...
(In reply to comment #9)
> Please change this bug as WON'T FIX and I will post a new bug report...

no, since this is another bug as yours so...
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.