[Bug 3502] Fatal: Read Error: Could not read or parse the JNLP file/ You can try downloading this file manually and sent it as bug report to ITWT.

bugzilla-daemon at icedtea.classpath.org bugzilla-daemon at icedtea.classpath.org
Wed Dec 20 09:29:56 UTC 2017


https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3502

JiriVanek <jvanek at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P5                          |P2
                 CC|                            |jvanek at redhat.com
          Component|IcedTea                     |NetX (javaws)
            Version|unspecified                 |hg
           Assignee|gnu.andrew at redhat.com       |jvanek at redhat.com
            Product|IcedTea                     |IcedTea-Web
           Severity|enhancement                 |normal

--- Comment #2 from JiriVanek <jvanek at redhat.com> ---
I see it differently:


javaws https://popgen.net/soft/lositan/code2/selwb.jnlp

....
Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Application Error:
Cannot grant permissions to unsigned jars. Application requested security
permissions, but jars are not signed.
...
Where the exception Is eprfectly justified. There are unsigned jars.


Why are you running "sudo javaws -jnlp '/home/julian/Documents/selwb4.jnlp'"  ?
*NEVER* run such applications as root! And it will not help with the issue with
unsigned jars. You can workaround it by --nosecurity, but be aware!
Why are you lunching local copy of file? As the jnlp file is designed to be
lunched over network, this one have a an clausule, that it download itself from
the host again. As your host is "nothing" it fails. This can be workarounded by
-Xnofork, but regular local file runs ITW with -Xoffline swithc, but even then
you should run it from original URL instead of file.

As for the topmost of your exception: access denied ("java.io.FilePermission"
"/usr/bin/xprop" "execute") - it is not form ITW. where it is from? From the
application itself? Strange, but might be.  I guess it is unsigned jar, without
permissions, (As result of wrong signing) , trying to execute xprop, and beeing
not allowed by ITW.

As for signing, being root of all evil here, I would recommend to try contact
the provider  of applciation and ask them to verify the signing - which may
lead   to discovering bug in ITW. 
Still, before doing it, please run the jnlp file correctly and investigate a
bit so you have something to say to them :)

Feel free continue asking here, as it indeed may run to the bug in iTW at the
end... (but currently I doubt)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20171220/943a7ddc/attachment.html>


More information about the distro-pkg-dev mailing list