[Bug 3383] Blank screen after loading applet

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3383

JiriVanek <jvanek at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from JiriVanek <jvanek at redhat.com> ---
Hi. "no changes have been made to the app or my system,"  Are you sure? Are you
sure the app was not updated? Are you sure your system was not updated over
night? Are you sure you did not logged into wayland session or something like
that?

That is one of the rare good things on computers. Once it is binary same, the
results are usually same :)

Do you have URL I can test? The url in logs is private.

I can see it is https.  In latest update of java (131), some legacy (insecure
algorithms) were dropped. This affects https. (however I can not see nay
related exception in logs)
How the appelt behaves with older jdk? How it behaves in epiphany/midori? But
as But htis part of logs looks really good. All was downloaded, and cache is
used correctly. 

The only bad in logs is:

java.security.AccessControlException: access denied
("java.util.logging.LoggingPermission" "control")
    at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
    at
java.security.AccessController.checkPermission(AccessController.java:884)
    at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
    at
net.sourceforge.jnlp.runtime.JNLPSecurityManager.checkPermission(JNLPSecurityManager.java:292)
    at java.util.logging.LogManager.checkPermission(LogManager.java:1586)
    at java.util.logging.Handler.checkPermission(Handler.java:310)
    at java.util.logging.Handler.setFormatter(Handler.java:122)
    at
com.ibm.tivoli.nm.logging.LogMaster.initConsoleLogger(LogMaster.java:296)
    at com.ibm.tivoli.nm.logging.LogMaster.<init>(LogMaster.java:213)
    at com.ibm.tivoli.nm.logging.LogMaster.init(LogMaster.java:153)
    at
com.ibm.tivoli.ncw.applets.common.AppletHelper.enableDebugging(AppletHelper.java:100)
    at
com.ibm.tivoli.ncw.applets.common.AbstractApplet.init(AbstractApplet.java:93)
    at sun.applet.AppletPanel.run(AppletPanel.java:435)
    at sun.applet.AppletViewerPanelAccess.run(AppletViewerPanelAccess.java:84)
    at java.lang.Thread.run(Thread.java:748)
WRITING 2: instance 1 status Start: applet not initialized.
plugin_in_pipe_callback
  PIPE: appletviewer wrote: instance 1 status Start: applet not initialized.
  PIPE: plugin read: instance 1 status Start: applet not initialized.
plugin_in_pipe_callback: setting status    Start: applet not initialized.



Which will be cause.  But I'm wondeinrg why.  What changed in your environment?
Something have.

-- 
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/20170516/697558eb/attachment.html>