Description of problem: When I try to start my typingcourse with Firefox I get the message: Applet not initialized Version-Release number of selected component (if applicable): Firefox 3.5.2 How reproducible: See below. Steps to Reproduce: 1. Go to: http://online3.typingmaster.com/tmonline3/login?id=unp5pb2f9 2. login with user 'test' and password 'geheim01' (just a trial-user ;-) ) 3. try to start the first lesson of the typing course Actual results: 'Applet not initialized' Expected results: I expect to see the lessons.. (It worked fine under Fedora 9) Additional info:
Created attachment 359502 [details] Screenprint with text 'Applet not initialized'
Shouldn't this go to Java component? Reassigning for further investigation.
Confirmed, starting firefox from a terminal produces: net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not initialize applet. at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:495) at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:441) at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:620) Caused by: java.lang.NullPointerException at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:481) ... 2 more Caused by: java.lang.NullPointerException at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:481) at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:441) at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:620) java.lang.NullPointerException at net.sourceforge.jnlp.NetxPanel.runLoader(NetxPanel.java:102) at sun.applet.AppletPanel.run(AppletPanel.java:380) at java.lang.Thread.run(Thread.java:636) java.lang.NullPointerException at sun.applet.AppletPanel.run(AppletPanel.java:430) at java.lang.Thread.run(Thread.java:636) with java-1.6.0-openjdk-plugin-1.6.0.0-27.b16.fc11.x86_64
I see the same: ICEDTEAPLUGIN_DEBUG=true firefox \ http://www.java.com/en/download/help/testvm.xml \ 2>&1 | tee console.log Writing to JVM: plugin PluginCookieInfo http://www.java.com/applet/testVM_en_US.properties gpName=javac%3ASupport%3AHelp%3Atestvm.xml; gpChannel=javac%3ASupport%3AHelp; gpServer=www.java.com; JSESSIONID=7f0c2885e168c0c256760463e922; s_cc=true; s_sq=%5B%5BB%5D%5D Wrote 247 bytes to pipe ICEDTEA PLUGIN: Instance::SendMessageToAppletViewer return Processing complete ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM return ICEDTEA PLUGIN: plugin_in_pipe_callback Received message: instance 1 status exception: java.lang.StringIndexOutOfBoundsException: String index out of range: 8. PIPE: plugin read: instance 1 status exception: java.lang.StringIndexOutOfBoundsException: String index out of range: 8. ICEDTEA PLUGIN: plugin_in_pipe_callback return ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM received message: instance 1 status exception: java.lang.StringIndexOutOfBoundsException: String index out of range: 8. Processing complete ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM return Pending event processed (this) ... 1 ICEDTEA PLUGIN: plugin_in_pipe_callback Received message: instance 1 status Start: applet not initialized. PIPE: plugin read: instance 1 status Start: applet not initialized. ICEDTEA PLUGIN: plugin_in_pipe_callback return ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM received message: instance 1 status Start: applet not initialized. Processing complete ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM return Pending event processed (this) ... 1 ^C Should i attach the whole log here?
java-1.6.0-openjdk-plugin-1.6.0.0-29.b16.fc11.x86_64
Per request, same error here, otherwise I have no troubles with OpenJDK that I'm aware of. java-1.6.0-openjdk-plugin-1.6.0.0-29.b16.fc11.x86_64
I tried to change data entries in Estonian business register (https://ettevotjaportaal.rik.ee/) and they use PKI smartcards with opensc to digitally authenticate and sign the requests with java applet. Authentication works flawlessly. Signing does not.
For clarification, authentication uses client side SSL certificates so that has nothing to do with java.
Can reproduce on Rawhide, neither http://www.java.com/en/download/help/testvm.xml nor http://java.com/en/download/installed.jsp?detect=jre&try=1 work as expected with java-1.6.0-openjdk-plugin-1.6.0.0-31.b16.fc12.x86_64 installed, Java enabled in the Firefox
Matej, feel free to clone this bug to rawhide if you're worried about the future releases/downstream products. The fact is, that this is completely broken in *production* version, which is more severe issue than unreleased development tree. Second fact is, that this prevents using some services, which is not a minor visual hickup and could be ignored.
This page works for me: http://java.com/en/download/installed.jsp?detect=jre&try=1 but this one does not: http://www.java.com/en/download/help/testvm.xml java-1.6.0-openjdk-plugin-1.6.0.0-31.b16.fc12.x86_64
The error in the original bug report is a parser bug, caused by the same issue that causes this: http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=406 As for http://www.java.com/en/download/help/testvm.xml not working -- that is a problem in the applet. The applet appears to be trying to do something like charAt(8) on the name/version string of the vm, which fails because IcedTea does not follow the exact same convention as Sun
I have just installed SUN-JAVA-jre and that is just working fine. OpenJDK disabled in Firefox. My problem is solved.
*** Bug 538640 has been marked as a duplicate of this bug. ***
Can you please try it again with this build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1841533 [F11-x86] http://koji.fedoraproject.org/koji/taskinfo?taskID=1841531 [F11-x86_64] You may have to use the --force option as the version numbers were not bumped I have temporarily mirrored the essential files here in case koji deletes files from the above build: http://dbhole.fedorapeople.org/java/
Deepak: F11-x86 still exhibits the same "Start: applet not initialized" problem with the java-1.6.0-openjdk-1.6.0.0-30.b16.fc11.i586.rpm and java-1.6.0-openjdk-plugin-1.6.0.0-30.b16.fc11.i586.rpm installed from http://koji.fedoraproject.org/koji/taskinfo?taskID=1841533 when testing at http://www.java.com/en/download/help/testvm.html
Jayson, try some other page with applet, that Sun's page is broken - which is very logical when you're trying to test compatibility. Tells quite a bit about that company. For me it fails too but other applets elsewhere start.
Some people here might find it interesting too, that Sun's java does not work currently in x86_64 as stated in: http://plugindoc.mozdev.org/faqs/java.html#Linux and i can cofirm it, it doesn't.
Jason: http://www.java.com/en/download/help/testvm.xml is not fixed by the new rpms, but the originally reported site (http://online3.typingmaster.com/tmonline3/login?id=unp5pb2f9) is. http://www.java.com/en/download/help/testvm.xml does not work due to a presumption by the applet that the jvm version string will be in format A.B.C_XY .. which is true for the Sun JVM, but not for IcedTea (the openjdk in Fedora). I have sent an email to the community requesting that we do the same with the IcedTea reported version. Once that is addressed, the applet should start working. The e-mail I sent is here: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2009-December/007712.html
Juha -- far be it from me to tout the Sun plugin :) ... But just for the record, Sun has finally introduced support for 64-bit systems as well. Their new plugin so is named libnpjp2.so. libjavaplugin_oji.so will not work for 64-bit.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I was able to load both the websites on x86_64 and x86 systems. Seems to work with the latest plugin. Try updating your system to the latest plugin. java version "1.6.0_18" OpenJDK Runtime Environment (IcedTea6 1.8) (fedora-41.b18.fc13-x86_64) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) java version "1.6.0_18" OpenJDK Runtime Environment (IcedTea6 1.8) (fedora-41.b18.fc13-i386) OpenJDK Server VM (build 14.0-b16, mixed mode) --Andrew
You mean latest to f11?
yes try upgrading your Icedtea to the latest version. Also note, the support for f11 ends in a few days (June 25, 2010), and no more updates for f11 will be provided. See comment 21 by Bug Zapper. Unless you upgrade to f12 or f13 and the bug persists with the latest version of icedtea, you should update the version number for this bug. -Andrew
I upgraded from F12 to F13 recently. And I was using Firefox with the new NP plugin but any Java applets were seeing incredible CPU usage but working. With the latest OpenJDK on F13 CPU usage is normal now, but some applets (for example the Facebook photo uploader) come up with this 'Applet not initialized' in the statusbar, and don't show up on the page.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.