From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17 i686; en-US; 0.6) Gecko/20001205 BuildID: 20001221 From 20.12.2000 CVS source build, following installation of Java plugin, Mozilla will not start - it bombs with "There was an error trying to initialize the HPI library". Reproducible: Always Steps to Reproduce: 1. Build Mozilla for sources - works fine, but need to get Java installed. 2. Go to local web page with Java applet, receive prompt to get the plugin. 3. After long download, the plugin reports that it has been successfully installed. 4. Java doesn't work immediately (prompts again to download plugin), so I close Mozilla. 5. Attempt to restart Mozilla, but it will not. Only fix from here is to delete the plugins/java2 directory etc. Errors on attempting to start Mozilla after apparently successful Java plugin installation: There was an error trying to initialize the HPI library Please check your installation, HotSpot does not work correctly when installed in the JDK 1.2 Linux Production Release, or with any JDK 1.1.x release. Could not startup JVM properly! java_vm process: could not start Java VM INTERNAL ERROR on Browser End: Could not read ack from browser System error?:: Resource temporarily unavailable My system is RH6.x release, updated kernel 2.2.17
Forgot to add that I have been able to reproduce this same problem using a few other versions of Mozilla - both M18 and 0.6 from binary distribution, also a version of each of those built from source.
Over to OJI for triage
Assignee: idk → edburns
Component: Java-Implemented Plugins → OJI
QA Contact: geetha.vaidyanaathan → shrir
This sounds a lot like the problem I had with RedHat 6.2 and which was fixed by upgrading to a newer version of glibc. The new glibc can be found at http://www.redhat.com/support/errata/RHSA-2000-057-04.html .
Thanks, Stephen, upgrading glibc seems to do the trick. Cheers ... I've set bug as FIXED.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.