Comment #12 on issue 16787 by behanz: Java Plugin not working
http://code.google.com/p/chromium/issues/detail?id=16787

Running chromium debug build rev.24046 on a purely 32bit gentoo system. Two  
java
plugins are provided:

/usr/share/java-config-2/nsplugin/sun-jdk-1.6-javaplugin.so ->
/opt/sun-jdk-1.6.0.14/jre/plugin/i386/ns7/libjavaplugin_oji.so
/usr/share/java-config-2/nsplugin/sun-jdk-1.6-plugin2-javaplugin.so ->
/opt/sun-jdk-1.6.0.14/jre/lib/i386/libnpjp2.so

I checked, firefox uses the first one (ns7/libjavaplugin_oji.so). I tried  
swapping it
for the plugin2, (libnpjp2.so), and it works too.

With chrome, the first one (ns7/libjavaplugin_oji.so) does not work at all.  
It
appears to not even provide a single mime-type in "about:plugins". No  
errors are
printed on the console.
The second one (libnpjp2.so) provides all the necessary details  
in "about:plugins",
but everytime it is read for information, it prints a lot of console  
messages
similiar to:
[29400:29401:4057703287048:WARNING:<chrome
dir>/src/webkit/glue/plugins/plugin_lib_linux.cc(54)] Couldn't parse plugin  
info:
application/x-java-applet
(and the same for application/x-java-bean, a bunch of messages for each)

When trying to launch a java applet, it fails with the above reported error  
message
"Didn't find JVM under <insert chrome plugin dir here>".


The plugin itself seems to check for %s/server/libjvm.so  
and %s/client/libjvm.so,
where %s is the directory where the plugin was started from.

My first wild guess would be that the plugin is supposed to be a symlink  
into the jvm
directory, and the plugin loader, before actually loading the plugin has to
readlink() all the way until it reaches the file itself. (which chrome  
doesn't do)
The plugin shared object is physically located exactly where the other  
files (libjvm
and friends) are present in the correct relative paths.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to