You are not logged in.
Whenever I try to access a page with an embedded java applet with Firefox, I only get a grey box instead of the applet. The grey box has the same size as the java applet would have. The CPU usage jumps up to 100% with the process `java` taking all the CPU usage. Closing the affected tab doesn't help. I must close firefox or kill the java-process to get back to normal CPU usage.
I'm using the newest official binary Firefox (3.0.6) and the OpenJDK6 version from the Arch Linux repositories (1.4.1-1). `about:config` in firefox shows the IcedTea-plugin listed as expected. I've also tried java with the latest Arch Linux Firefox Gran Paradiso but had the same behavior.
Using java from the commandline without firefox being involved works fine.
Using konqueror with the IcedTea-plugin works partly. Some very small applets like on (javatester.org) worked, others as the official Sun testing applets or an IRC-applet didn't.
If I use the proprietary java plugin everything (including embedded in firefox) works fine.
Of course I could just install the proprietary java package, but as most people say that OpenJDK is feature complete and should work without problems for everyone I would love to do so. Unfortunately I couldn't find any further information on my problems, so I hope someone of you might have an idea.
Oh, and I have a 32-bit CPU and am therefore using 32-bit Arch Linux.
Offline
same problem...I think...i go back to proprietary jdk! But many applications are using openjdk...:( what to do?
Last edited by virusso80 (2009-03-01 07:52:38)
Offline
please test if it also happens with former 1.4 pkg. then go and contac upstream developers where changes happened that caused it. the best way is always to ask upstream if you cannot find a packaging bug.
Offline
I just tried openjdk6 versions 1.3.1 and 1.4
With both versions I don't have the problem of 100% CPU usage but java still doesn't work.
In 1.4 I get following message in the firefox status bar "Start: applet not initialized". The java process starts and keeps running.
In 1.3.1 I get a "Done" message and while this message is shown the java process runs. A second after that I get a "starting applet" message in the statusbar and the java process isn't running anymore.
The process of java as given by `ps ax` is "/usr/lib/jvm/java-1.6.0-openjdk/jre/lib/i386/../../bin/java sun.applet.PluginMain"
The behavior in konqueror doesn't change with these older versions. The process started by konqueror is: "java -classpath /usr/share/apps/kjava/kjava.jar -Dhttp.proxyHost=192.168.2.1 -Dhttp.proxyPort=8080 -Djava.security.manager=org.kde.kjas.server.KJASSecurityManager -Djava.security.policy=/usr/share/apps/kjava/kjava.policy org.kde.kjas.server.Main"
Offline
Hmm, in my case, I backed off to openjdk6-1.4-2-x86_64.pkg.tar.gz and got the correct behavior (e.g. http://www.time.gov/timezone.cgi?Pacific/d/-8/java). The newer package openjdk6-1.4.1-1-x86_64.pkg.tar.gz gives me the blank box as the OP reported. I didn't notice 100% CPU usage, but I didn't particularly look. Not sure if this is helpful, but just one more data point.
Mike
Linux User #353 - SLS -> Slackware -> Red Hat -> Mandrake -> Fedora -> Arch
Offline
Same problem with the last 1.4.1-1 x86_64, I was able to run one web applet with a standalone sun-jmv 64bit, but for all others it's impossible to retrive the trust certificate and run
P.S. Previous openjdk worked fine ...
Last edited by Yagi858 (2009-03-04 13:54:38)
Offline
There's a thread with the same problem. It's a Java toolkit issue, so you should report it upstream. The same thing happens with jabref+dwm/awesome/etc., btw.
EDIT: Oh, wait, I only meant the grey box thing. The applet is still there actually, it's just... well... invisible. Kinda.
Last edited by Runiq (2009-03-04 17:42:37)
Offline
Everything seems to be fixed after last update. Please check and mark as SOLVED
Offline
If the update doesn't fix it, check the AwesomeWM wiki FAQ. There's discussion there that I added to a bit on how to fix the grey box problem there, which may or not be the same problem as this.
Offline
Well the update fixes the CPU problem, but I still have the grey box problem. So actually I had two problems before, the one also addressed by the other thread.
Ranguvar: What AwesomeWM wiki FAQ are you talking about?
Offline
http://awesome.naquadah.org/wiki/index. … _screen.21
Last edited by Ranguvar (2009-03-12 23:48:46)
Offline
Well the update fixes the CPU problem, but I still have the grey box problem. So actually I had two problems before, the one also addressed by the other thread.
There is a little utility on suckless.org called wmname. Use it to change your wm's name to LG3D, and at least stand-alone Java apps should work again (I'm not sure for those Java applets or whatchamacallit in firefox, though).
Note that this is still a workaround until the Java devs finally patch it up.
Offline
Thanks for the link. I've now tested the ways described in the awesomeWM wiki and none works for me.
I've tested to set AWT_TOOLKIT=MToolkit but it doesn't help and I've also tried to start firefox within a nested X-Server but I still got a gray box.
And using standalone java works fine for me, I only get the gray box problems with embedded java applets. So I haven't tested the wmname method.
I think I'll just wait for another version and hope to have my problems resolved. Thanks for your help folks!
Offline
Don't set AWT_TOOLKIT, and add 'wmname LG3D' somewhere so that you can type 'wmname' at a terminal before you try a Java app and the response will be 'LG3D'.
Offline
So I now installed wmname and put the wmname LG3D to my .bashrc but still no luck with java applets in firefox.
Something I also noticed is that I get a bunch of Java errors in bash if I start firefox within a bash:
java.lang.RuntimeException: Failed to handle message: handle 14778979 Thread[Thread-1,5,main]
at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:439)
at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:290)
at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:72)
Caused by: java.lang.NullPointerException
at sun.applet.PluginAppletViewer.<init>(PluginAppletViewer.java:312)
at sun.applet.PluginAppletViewerFactory.createAppletViewer(PluginAppletViewer.java:120)
at sun.applet.PluginAppletViewer.parse(PluginAppletViewer.java:1560)
at sun.applet.PluginAppletViewer$7.run(PluginAppletViewer.java:1484)
at java.security.AccessController.doPrivileged(Native Method)
at sun.applet.PluginAppletViewer.parse(PluginAppletViewer.java:1493)
at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:413)
... 2 more
net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not initialize applet.
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:472)
at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:418)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:597)
Caused by: java.lang.NullPointerException
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:458)
... 2 more
Caused by:
java.lang.NullPointerException
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:458)
at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:418)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:597)
java.lang.NullPointerException
at net.sourceforge.jnlp.NetxPanel.runLoader(NetxPanel.java:100)
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)
Offline