Error using icedtea-7 in Linux Mint 17

[maxcel]

I use webmin to remotely access my server and it requires java to display the file manager. Since changing from Mint 13 to 17 I am getting a persistent error screen from the icedtea and cannot view the file manager. I have printed the error report but it means nothing to me. Please can anybody help?

• IcedTea-Web Plugin version: 1.5 (1.5-1ubuntu1)
  Tue Aug 05 13:48:21 BST 2014
  net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not initialize applet. For more information click "more information button".
  at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:746)
  at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:675)
  at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:908)
  Caused by: net.sourceforge.jnlp.LaunchException: The applet is signed but its manifest specifies Sandbox permissions. This is not yet supported. Try running the applet again, but choose the Sandbox run option.
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkPermissionsAttribute(ManifestAttributesChecker.java:206)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkAll(ManifestAttributesChecker.java:79)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:288)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.createInstance(JNLPClassLoader.java:351)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:418)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:394)
  at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:711)
  ... 2 more
  Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Run in Sandbox call performed too late. The classloader was notified to run the applet sandboxed, but security settings were already initialized.
  at net.sourceforge.jnlp.runtime.JNLPClassLoader$SecurityDelegateImpl.setRunInSandbox(JNLPClassLoader.java:2385)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkPermissionsAttribute(ManifestAttributesChecker.java:203)
  ... 8 more
  
  Chain:
  1) at Tue Aug 05 13:48:12 BST 2014
  net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Run in Sandbox call performed too late. The classloader was notified to run the applet sandboxed, but security settings were already initialized.
  at net.sourceforge.jnlp.runtime.JNLPClassLoader$SecurityDelegateImpl.setRunInSandbox(JNLPClassLoader.java:2385)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkPermissionsAttribute(ManifestAttributesChecker.java:203)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkAll(ManifestAttributesChecker.java:79)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:288)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.createInstance(JNLPClassLoader.java:351)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:418)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:394)
  at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:711)
  at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:675)
  at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:908)
  2) at Tue Aug 05 13:48:12 BST 2014
  net.sourceforge.jnlp.LaunchException: The applet is signed but its manifest specifies Sandbox permissions. This is not yet supported. Try running the applet again, but choose the Sandbox run option.
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkPermissionsAttribute(ManifestAttributesChecker.java:206)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkAll(ManifestAttributesChecker.java:79)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:288)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.createInstance(JNLPClassLoader.java:351)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:418)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:394)
  at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:711)
  at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:675)
  at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:908)
  Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Run in Sandbox call performed too late. The classloader was notified to run the applet sandboxed, but security settings were already initialized.
  at net.sourceforge.jnlp.runtime.JNLPClassLoader$SecurityDelegateImpl.setRunInSandbox(JNLPClassLoader.java:2385)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkPermissionsAttribute(ManifestAttributesChecker.java:203)
  ... 8 more
  3) at Tue Aug 05 13:48:12 BST 2014
  net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not initialize applet. For more information click "more information button".
  at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:746)
  at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:675)
  at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:908)
  Caused by: net.sourceforge.jnlp.LaunchException: The applet is signed but its manifest specifies Sandbox permissions. This is not yet supported. Try running the applet again, but choose the Sandbox run option.
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkPermissionsAttribute(ManifestAttributesChecker.java:206)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkAll(ManifestAttributesChecker.java:79)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.<init>(JNLPClassLoader.java:288)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.createInstance(JNLPClassLoader.java:351)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:418)
  at net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:394)
  at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:711)
  ... 2 more
  Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Run in Sandbox call performed too late. The classloader was notified to run the applet sandboxed, but security settings were already initialized.
  at net.sourceforge.jnlp.runtime.JNLPClassLoader$SecurityDelegateImpl.setRunInSandbox(JNLPClassLoader.java:2385)
  at net.sourceforge.jnlp.runtime.ManifestAttributesChecker.checkPermissionsAttribute(ManifestAttributesChecker.java:203)
  ... 8 more

[ilagi]

I had the same, it is an IcedTea bug, but there is a workaround which worked for me:

For any visitors that come across this bug report before the issue is properly resolved, this issue can be worked around in the following manner:

(1) Open the IcedTea-Web settings control panel (itweb-settings or itweb-settings.itweb)

(2) Click "Certificates" on the left

(3) Select "Trusted Certificates" in the dropdown box

(4) Remove all of the certificates

This will cause all signed applets to display a security warning dialog again before running, rather than being automatically trusted. The next time you run a signed applet, do the following: Uncheck the "Always trust" checkbox if it is checked; Select the "Run" option; If the applet fails to run, examine the error message. If you see the following message:

"Caused by: net.sourceforge.jnlp.LaunchException: The applet is signed but its manifest specifies Sandbox permissions. This is not yet supported. Try running the applet again, but choose the Sandbox run option."

this indicates that the applet you are trying to run is signed and specifies Sandbox permissions in its manifest's Permissions attribute, and IcedTea-Web's lack of support for this configuration is the issue tracked by this bug report. A fix is currently in progress, however there is a workaround, which is described in the above failure message.

Run the applet again, deselect the "Always trust" checkbox, and click the "Sandbox" button. The applet should then run normally. If it does not, please open a new bug report and attack the stack trace from that failure.

[Habitual]

I had the same, it is an IcedTea bug, but there is a workaround which worked for me:

For any visitors that come across this bug report before the issue is properly resolved, this issue can be worked around in the following manner:

(1) Open the IcedTea-Web settings control panel (itweb-settings or itweb-settings.itweb)

(2) Click "Certificates" on the left

(3) Select "Trusted Certificates" in the dropdown box

(4) Remove all of the certificates

This will cause all signed applets to display a security warning dialog again before running, rather than being automatically trusted. The next time you run a signed applet, do the following: Uncheck the "Always trust" checkbox if it is checked; Select the "Run" option; If the applet fails to run, examine the error message. If you see the following message:

"Caused by: net.sourceforge.jnlp.LaunchException: The applet is signed but its manifest specifies Sandbox permissions. This is not yet supported. Try running the applet again, but choose the Sandbox run option."

this indicates that the applet you are trying to run is signed and specifies Sandbox permissions in its manifest's Permissions attribute, and IcedTea-Web's lack of support for this configuration is the issue tracked by this bug report. A fix is currently in progress, however there is a workaround, which is described in the above failure message.

Run the applet again, deselect the "Always trust" checkbox, and click the "Sandbox" button. The applet should then run normally. If it does not, please open a new bug report and attack the stack trace from that failure.

You sir, rock!

[unprinted]

I had the same, it is an IcedTea bug, but there is a workaround which worked for me:

..

Run the applet again, deselect the "Always trust" checkbox, and click the "Sandbox" button. The applet should then run normally.

Erm, what "Sandbox" button? I don't see one (and so it's not running the Webmin File Manager...)