Bug 684974
Summary: | jnlp.LaunchException: Fatal: Initialization Error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Donald Cohen <don-redhat-z6y> |
Component: | java-1.6.0-openjdk | Assignee: | Omair Majid <omajid> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 14 | CC: | ahughes, dbhole, jvanek, langel, lkundrak, mjw, mmatejov, omajid |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-26 18:11:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Donald Cohen
2011-03-14 21:42:34 UTC
Now that I've figured out how to get the output from chrome, here it is: [5068:5068:4315073909859:ERROR:extension_prefs.cc(734)] Bad or missing pref 'state' for extension 'hpibmhghjndideebpackbdlpncgkcppp' [5068:5068:4315073910171:ERROR:extension_prefs.cc(734)] Bad or missing pref 'state' for extension 'lncjcfkpannmofmpgdfoonkniofdnaba' java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.7) (fedora-52.1.9.7.fc14-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not initialize applet. at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:604) at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:548) at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:729) Caused by: java.lang.NullPointerException at net.sourceforge.jnlp.runtime.JNLPClassLoader.initializeResources(JNLPClassLoader.java:427) at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:168) at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:249) at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:575) ... 2 more Caused by: java.lang.NullPointerException at net.sourceforge.jnlp.runtime.JNLPClassLoader.initializeResources(JNLPClassLoader.java:427) at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:168) at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:249) at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:575) at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:548) at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:729) java.lang.NullPointerException at net.sourceforge.jnlp.NetxPanel.runLoader(NetxPanel.java:99) 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) java.lang.Exception: Applet initialization timeout at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:637) at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270) at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82) java.lang.RuntimeException: Failed to handle message: handle 85983265 for instance 1 at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:660) at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270) at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82) Caused by: java.lang.Exception: Applet initialization timeout at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:637) ... 2 more Looks the same, but there have been times in the past when one worked and the other didn't. Sorry for the re-assignment back and forth. The problem does appear to be in the JNLP classloading code. Re-assigning back to Omair. Fixed in IcedTea-Web: http://icedtea.classpath.org/hg/icedtea-web/rev/df3cf32781d3 As usual, I'd like to know when I should expect to see the fix in yum updates and how I can recognize it when I do. I guess the next time I see openjdk in an update I'll try it. Any estimate? Hi Donald. The fix will be in F15/rawhide before the beta deadline (29th). As for current Fedora version, we want to let icedtea have a bit of exposure before backporting it to existing stable releases, so I would guess some time in May/early June. Deepak, I didn't think there was any plan to change existing stable releases and it's something I'd be against. In about eight months, those releases without IcedTea-Web (F13 + F14) will be dead anyway. |