Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

ibm java plugin failure

  • 3 antwurd
  • 8 hawwe dit probleem
  • 14 werjeftes
  • Lêste antwurd fan mozillar

more options

Before version 368, firefox recognised the ibm java plugin. Now, ibm java plugin not recognised

Before version 368, firefox recognised the ibm java plugin. Now, ibm java plugin not recognised

Alle antwurden (3)

more options

Firefox 3.6 versions only work with the Next Generation Java Plugin.

http://java.sun.com/javase/downloads/index.jsp#jdk (you need JRE) NOTE]: The Firefox 3.6 browser requires Java SE 6 Update 10 or later. Otherwise, Java-based web applications will not work.
http://java.com/en/download/faq/firefox_newplugin.xml
http://java.sun.com/javase/6/webnotes/install/jre/manual-plugin-install-linux.html
more options

Please pay attention and be aware that this error concerns ibm java; the answer is available here: (http://www.ibm.com/developerworks/forums/thread.jspa?threadID=337317&tstart=0)

more options

incomptability between ibm java sdk6 and firefox 368 Posted: Aug 13, 2010 06:48:05 AM Click to report abuse... Click to reply to this thread Reply Firefox368 now needs this plugin libnpjp2.so as described by oracle (http://www.oracle.com/technetwork/java/javase/manual-plugin-install-linux-136395.html). This plugin is not available in ibmjavasdk6 ther

Posts: 3 Registered: Oct 20, 2009 08:31:26 AM

Re: incomptability between ibm java sdk6 and firefox 368 Posted: Aug 13, 2010 06:52:34 AM in response to: ther in response to: ther's post Click to report abuse... Click to reply to this thread Reply Now realised that this plugin is located in /path/to/java/jre/lib/i386/, so a symbolic link was created. Documentation should be changed accordingly.