Red Hat Bugzilla – Bug 485386
Seamonkey is incompatible with the SUN Java plugin
Last modified: 2011-10-20 08:32:34 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. make sure the packages above are installed
2. launch seamonkey
3. visit a page with a java applet, e.g.
Running java applet, or at least a decent error message.
This is a new problem, the 64bit SUN plugin didn't exist earlier. In fact, we haven't released it yet. But it works great with firefox, even out-of-the-box with the RPM above. It's just seamonkey that accepts it as a valid plugin (see about:plugins), but crashes when it attempts to use it.
Seamonkey 1.0.x and 1.1.x fails to exchange NPAPI callback table with the java plugin...2.0a works fine. Looks like some misconfiguration...
the 64-bit plugin ignores all old mozilla browsers (1.8.0 and 1.8.1), returns NPERR_INCOMPATIBLE_VERSION_ERROR from NP_Initialize().
We can cosider to hack the plugin interface or at least fix crash of the old seamonkey.
It will be fixed when Bug 460417 lands.
java-1.6.0-sun-plugin-18.104.22.168-1jpp.1.el4 + seamonkey-1.0.9-61.el4 = no crash. Yay! Applets still don't work, but I guess that won't get better until Seamonkey is rebased. There's one thing that could be improved in the meantime, though: when a page with an applet is visited, a dialog pops up asking me if I want to download the appropriate plug-in for application/x-java-vm. When I click OK, seamonkey goes to http://www.propeller.com/plugins/jvm.html, which gives 404: Page not Found. That's not helpful.
FTR, we've just switched to libnpjp.so also in case of the 32-bit Sun java plugin.
We're not going to fix in in seamonkey on RHEL4.