Closed Bug 225102 Opened 21 years ago Closed 19 years ago

1.6 Mozilla breaks Java for all other installed mozillas. firebird.reg fixes it, but why ?

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jou, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030 I hav Mozilla 1.2.1/1.3/1.4.1/1.5/1.6a installed parralel on my system, each one using it's own subdirectory of course. With Mozilla 1.6 java wasn't recognized any more, showed up in about:plugins. Java then didn't work with any of the older versions of Mozilla too. I had to import the firebird.reg to make it work, probably the [HKEY_LOCAL_MACHINE\SOFTWARE\mozilla.org\Mozilla] "CurrentVersion"="1.5" was needed. But why ? And why does this break Java for all older Versions of Mozilla on the machine ? This strangeness did cost me quite some time on 3 Machines. Reproducible: Always Steps to Reproduce: 1. Remove HKEY_LOCAL_MACHINE\Software\Mozilla, check about:plugins to verify java. 2. Use 1.6a build on http://www.heise.de/security/dienste/browsercheck/tests/java.shtml 3. Java is not started. it shows "click here for plugin", although the .dll helpers are at the right place. Actual Results: Nothing. Expected Results: Website should say "Java ist AKTIV!" without hacking 'round the registry before.
Addendum: HKEY_LOCAL_MACHINE\SOFTWARE\mozilla.org has to be removed to reproduce. [HKEY_LOCAL_MACHINE\SOFTWARE\mozilla.org\Mozilla] "CurrentVersion"="1.5" Makes java work _without_ restarting mozilla, just page reload is enough.
[HKEY_LOCAL_MACHINE\SOFTWARE\mozilla.org\Mozilla] "CurrentVersion"="" Note that the value can even be empty, and java works. removing/renaming the CurrentVersion registry entry disables Mozilla-Java.
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: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.