Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 15160 - Mozilla Java Plugin not working
Summary: Mozilla Java Plugin not working
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Java team
URL:
Whiteboard:
Keywords:
: 12805 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-02-05 07:11 UTC by Ilkka Urtamo
Modified: 2003-03-31 10:28 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilkka Urtamo 2003-02-05 07:11:41 UTC
With all available jdk/jre's, it is not possible to get javaplugin working in
mozilla.
Blackdown,ibm and sun java's give same/similar unresolved externals.

Example:
LoadPlugin: failed to initialize shared library
/opt/ibm-jre-1.3.1/bin/libjavaplugin_oji.so
[/opt/ibm-jre-1.3.1/bin/libjavaplugin_oji.so: undefined symbol:
__vt_17nsGetServiceByCID]
LoadPlugin: failed to initialize shared library
/opt/ibm-jre-1.3.1/bin/libjavaplugin_oji.so
[/opt/ibm-jre-1.3.1/bin/libjavaplugin_oji.so: undefined symbol:
__vt_17nsGetServiceByCID]


- Gentoo Base System version 1.4.2.8
- Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030125
- build options: -athlon-tbrd -O3 -pipe
- ibm-jdk/jre  (portage V) 1.3.1-r1
Comment 1 Artur Brodowski 2003-02-05 08:54:09 UTC
is mozilla based on gtk1.2 or gtk2?
you could compile sun's j2sdk (which is in portage tree); that will give you working java plugin, at least in the second case (although i had to link plugin libraries manually).
Comment 2 Ilkka Urtamo 2003-02-05 09:17:41 UTC
all i know is:


*  x11-libs/gtk+
      Latest version available: 2.2.0
      Latest version installed: 2.2.0

maybe this is bug for doc project to update java howto?
Comment 3 Artur Brodowski 2003-02-05 09:37:24 UTC
well i suppose you use gtk1.2 based mozilla, since latest build require
gtk2 to be forced, and you would remember that ;)
afair in that case blackdown's and sun's java plugins worked fine, 
but this also might be gcc related issue (mozilla being compiled
with gcc-3.2.x and java vm with gcc 2.95...)

you can try these:
- are you sure you've updated your environment (java-config) afrer emerging
blackdown/sun jre/jdk?
- try to copy/link plugin libraries manually directly to mozilla plugin
directory (/usr/lib/nsbrowser/plugins or sth like this).
- if above fail, emerge sun-j2sdk, that will compile java vm on your box
with latest gcc and plugins will work (checked).

regards,
artb.
Comment 4 brian tarricone 2003-02-07 15:05:59 UTC
that's interesting... i can't get this to work at all.  before i had just tried using the binary distributions of the jdk (sun-jdk, blackdown-jdk, etc.).  i just read this bug here, and tried emerging sun-j2sdk.  compiled just fine, used java-config to set the j2sdk, ran env-update, sourced /etc/profile, verified the path was correct, and linked the plugin to my plugins directory, but no go:

LoadPlugin: failed to initialize shared library /opt/sun-j2sdk-1.4.1/jre/plugin/i386/ns610/libjavaplugin_oji.so [/opt/sun-j2sdk-1.4.1/jre/plugin/i386/ns610/libjavaplugin_oji.so: undefined symbol: _ZN16nsServiceManager23GetGlobalServiceManagerEPP17nsIServiceManager]

now the difference is that i'm running a copy of mozilla that i compiled myself from mozilla CVS - the date i have on it is feb 1st. could this have something to do with it?
Comment 5 brian tarricone 2003-02-07 15:12:37 UTC
argh - sorry about the wrapping - let's try again...

that's interesting... i can't get this to work at all.  before i had just tried
using the binary distributions of the jdk (sun-jdk, blackdown-jdk, etc.).  i
just read this bug here, and tried emerging sun-j2sdk.  compiled just fine, used
java-config to set the j2sdk, ran env-update, sourced /etc/profile, verified the
path was correct, and linked the plugin to my plugins directory, but no go:

LoadPlugin: failed to initialize shared library
/opt/sun-j2sdk-1.4.1/jre/plugin/i386/ns610/libjavaplugin_oji.so
[/opt/sun-j2sdk-1.4.1/jre/plugin/i386/ns610/libjavaplugin_oji.so: undefined
symbol: _ZN16nsServiceManager23GetGlobalServiceManagerEPP17nsIServiceManager]

now the difference is that i'm running a copy of mozilla that i compiled myself
from mozilla CVS - the date i have on it is feb 1st. could this have something
to do with it?
Comment 6 brian tarricone 2003-02-15 22:17:23 UTC
very odd - i recompiled mozilla (from cvs, after updating), and now the sun-j2sdk
version of the java plugin loads fine.  i didn't recompile it or anything, all i
did was update to a newer mozilla.
Comment 7 Brad Laue (RETIRED) gentoo-dev 2003-02-23 15:33:59 UTC
This plugin worked with Gentoo 1.2; as soon as I rebootstrapped with GCC3 and used the 1.4 profile (and rebuild all packages) I encountered this bug. 

I notice that the ebuild for mozilla enables ABI compatibility with older compiler versions, but this doesn't seem to have had any effect.

Both sun and blackdown JDK's fail as per the previous posters. Hard to pin this down. Could it be GCC? GLIBC 2.3.1? ANy thoughts?
Comment 8 Brad Laue (RETIRED) gentoo-dev 2003-02-23 15:37:18 UTC
http://bugzilla.mozilla.org/show_bug.cgi?id=116444

Should add this, too. The discussion on this bug indicates it's an issue relating to GCC3.
Comment 9 Dan Mosedale 2003-02-25 00:14:29 UTC
Note, in particular, comment 92 in that bug:

The new java plugin from blackdown works with gcc-3.2. Download from
http://www.blackdown.org/java-linux/mirrors.html (not all mirrors have it yet,
though) They ship two builds; one for gcc 3.2 and one for gcc-2.95. The gcc-2.95
build will stop being made at some point in the future, apparently.
Comment 10 Brad Laue (RETIRED) gentoo-dev 2003-02-25 01:23:44 UTC
With regard to that, I discovered this in the blackdown-jdk-1.4.1 ebuild:

if [ "`gcc-major-version`" -eq "3" -a "`gcc-minor-version`" -ge "2" ] ; then
    SRC_URI="x86? ( ${J_URI}/i386/${JREV}/j2sdk-${PV}-${JREV}-linux-i586-gcc3.2.bin )"
else
    SRC_URI="x86? ( ${J_URI}/i386/${JREV}/j2sdk-${PV}-${JREV}-linux-i586-gcc2.95.bin )"

And so on, for each supported architecture. If a few people would test this out (use ACCEPT_KEYWORDS="~x86" to emerge it) and report on its success that would be great - it worked on my system, but multiple success reports would be better.

Comment 11 Stephen Degler 2003-03-02 20:10:57 UTC
Blackdown jdk 1.4.1 is working on mozilla 1.2.1 all compiled with gcc 3.2.2
Comment 12 Bug Hunter 2003-03-04 19:04:01 UTC
i have to add a "works for me too"

mozilla-1.2.1-r5
blackdown-jdk-1.4.1
java-config-0.2.7

gcc-config-1.3.1
gcc-3.2.2

and i even got into hushmail with a slight modification
(see bug #16859)
Comment 13 Adrian Almenar 2003-03-13 00:19:02 UTC
*** Bug 12805 has been marked as a duplicate of this bug. ***
Comment 14 Bret Towe 2003-03-31 01:36:27 UTC
im using blackdown-jdk 1.4.1 with moz 1.3 and galeon 1.2.9
working great havent had a problem with java at all
Comment 15 Ilkka Urtamo 2003-03-31 01:41:14 UTC
Ok.. Had this working also with blackdown 1.4 and mo1.3
I gues this one has been fixed
Comment 16 Brad Laue (RETIRED) gentoo-dev 2003-03-31 09:49:13 UTC
This isn't fixed. If it were, blackdown JDK and JRE 1.4.1 would be marked stable. 

Would a maintainer please mark them stable? They've been in use for a long
time with no showstoppers. This is an important component of a functional 
system.
Comment 17 Ilkka Urtamo 2003-03-31 10:28:12 UTC
Sorry (: 
Didnt actually know when one is allowed to set something as solved. I started it so i tought im the one setting it to "solved" 

Sorry about the inconvenience.