Closed Bug 23672 Opened 25 years ago Closed 25 years ago

Java is not enabled after installation

Categories

(Core Graveyard :: Java: OJI, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: pawyskoczka, Assigned: edburns)

References

()

Details

(Whiteboard: [PDT+]w/b minus on 03/03- waiting update from Stanley; current estimate is 2/24-2/29 ETA, Waiting to get access to installer to test.)

Build: 2000011108 on Windows JRE 1.3 Steps: 1. Removed Seamonkey and JRE 1.3 from PC 2. Installed Seamonkey and JRE 1.3 3 Rebooted PC 4. The plugins folder was created and the java dll were copied to the plugins folder 5. Loaded the url http://www.javasoft.com/applets/other/Bubbles/index.html 6. Applet does not load. Java is not enabled. Expected - the Java applet to load Actual - Java applet does not load This particular bug is related to Windows. This what happens after bug # 21943 was fixed.
Added Eric to the cc list.
Target Milestone: M13
We need this fixed ASAP. Putting on M13 radar.
This might have some relationship to the following changes, or it might not. FYI, bug #21943 has been fixed, so a plugins directory is now being created by the installer. The existing plugin search logic searches only in the Mozilla plugins directory if one exists; if one is not found, it falls back to the Nav4 plugins directory. av will fix open bug #21938 for M13 so the logic will *first* check the Mozilla plugins directory if it exists, and if not (or the plug-in is not found there) then fall back to checking the Nav4 plugins directory. However, the Mozilla plugins directory is the only place you would expect to find the OJI plug-in stub anyway, so this bug is probably an independent problem in which the OJI stub isn't being detected for some reason. Adding av to cc: list to be safe.
Target Milestone: M13 → M14
move to m14. let me know if fixes are available. thx.
Nominating for official beta1 consideration. If Java does not work in Beta 1, it will be bad for Sun, Netscape, and Java.
Keywords: beta1
*** Bug 21757 has been marked as a duplicate of this bug. ***
I don't see java start or applets run after selecting java in the commercial build installer on the 2/1/00 win32 builds.
Chris this has been broken for a while in M13. Waiting for a new JRE 1.3. ed.burns@SUN.Com will is sent a testing version but I was unable to downlown it.
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
Summary: [Beta1] Java is not enabled after installation → Java is not enabled after installation
This bug depends on 26875.
Depends on: 26875
Updating the bug dependency on this one, since bug # 26875 was marked as a duplicate of bug 27486. The current milestone for fixing 27486 is M15, which would prevent this bug from being fixed in M14.
Depends on: 27486
No longer depends on: 26875
Adding Ed Burns to the CC list on this one, for verification when Java Plug-In is claimed to work.
Since we seem to be using this bug as a [META] tracking bug for "what we have to do to get Java working again," adding dependencies on bug 27755, bug 27462, and bug 27763.
Depends on: 27462, 27755, 27763
Whiteboard: [PDT+] → [PDT+] Awaiting update from Stanley; current estimate is 2/24-2/29 ETA
Must fix by 03/03 or will not make the beta1 train.
Whiteboard: [PDT+] Awaiting update from Stanley; current estimate is 2/24-2/29 ETA → [PDT+] Must fix 03/03- waiting update from Stanley; current estimate is 2/24-2/29 ETA
Whiteboard: [PDT+] Must fix 03/03- waiting update from Stanley; current estimate is 2/24-2/29 ETA → [PDT+]w/b minus on 03/03- waiting update from Stanley; current estimate is 2/24-2/29 ETA
This bug still depends on 27462, 27486, 27755, 27763. However, I have put in several workaround in Java Plug-in code, so at least the applets will start up with M14.
I can test this tommorow, hopefully.
Assignee: drapeau → edburns
Actually, I can't test it since I don't have access to the installer. Is the installer you mention part of SeaMonkey? Is it possible for me to build the installer without too much work so I can test it? After building mozilla code from 5pm on 02/24/00 with MOZ_DEBUG=1, I observe the same behavior as in 27486.
Whiteboard: [PDT+]w/b minus on 03/03- waiting update from Stanley; current estimate is 2/24-2/29 ETA → [PDT+]w/b minus on 03/03- waiting update from Stanley; current estimate is 2/24-2/29 ETA, Waiting to get access to installer to test.
Adding michaell, PM for Installer, to cc: list. Michael, how can we enable Sun to test the Installer's behavior in a timely way when they change their code?
I installed Java in today's build (2000022708 - build numbers are still screwed up, this was on 3/1), and I went to several pages with applets including games.yahoo.com and the reference page for this bug. Worked for me. Can we call this one fixed?
I confirm that I too can get applets to work. I concurr with michaell. I'm Calling it fixed. Here are the steps I took to test that it was fixed: 02 March 00 Here are the steps I took to enable the viewing of applets in mozilla. STEP 8 IS THE MOST IMPORTANT, and UNUSUAL step. 1. Check tinderbox to see that it's green for win32 clobber 2. Checkout SeaMonkey at around 11:30am on 02 March 2000 3. Built Mozilla with MOZ_DEBUG=1 4. Used the WINNT Add/Remove programs feature to remove any JRE and JDK instance I had installed on my machine. Then I rebooted. 5. Used a find command to make sure there were no instances of any of the following files on my C: drive: jpins32.dll npjava*.dll jpishare.dll jaws.jar This step is also intended to catch the case where you have Netscape Navigator 4.x with the Java plugin installed, which I don't. If you do, you must make sure that you don't have the plugin installed. 6. Downloaded the JRE Release Candidate (RC) 1 release by visiting: http://developer.java.sun.com/developer/earlyAccess/j2sdk13/ And choosing the "One large bundle" option under the heading Internationalized version of Java 2 Runtime Environment 7. Ran the installer exe. 8. Unzipped George's zip file on top of the install location, which for me was C:\Program Files\JavaSoft\JRE\1.3 . 9. Copied C:\Program Files\JavaSoft\JRE\1.3\bin\npjava*.* to my mozilla plugins directory, which is: D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\plugins 10. Ran D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\mozilla.exe After doing the profile manager dance, I was able to view applets without java-related crashes.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I can confirm as well, on Win98. I just completed a build (did a pull around 11:30AM today, just finished building) and applets work.
So, just out of curiosity, how come this is working for me without going through the profile dance?
Now works with the patch applied.
By "profile dance" I'm referring to the fact that MOZ_DEBUG=1 builds force one to use the mozilla profile manager. If you built without MOZ_DEBUG=1, then you only have to do the profile dance if you removed your mozregistry.dat file and then restarted mozilla.
Verified in the 2000030609 build.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.