Closed Bug 208573 Opened 21 years ago Closed 21 years ago

Mozilla fails to load The Java Plugin on application launch

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: grindel1, Assigned: joshua.xia)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425

LoadPlugin: failed to initialize shared library
/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so
[/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so: undefined symbol:
_ZN16nsServiceManager23GetGlobalServiceManagerEPP17nsIServiceManager]

Directory structure of mozilla and plugin.

/usr/local/mozilla/plugins
lrwxrwxrwx    1 root     root           58 Jun  6 15:09 javaplugin_oji.so ->
/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so*


/usr/local/j2re1.4.1/plugin/i386/mozilla/
-rwxr-xr-x    1 1000     1000       249861 Jan 13 11:03 javaplugin_oji.so*

As far as I know the plugin is installed properly 

Please Contact me grindel1@yahoo.com for any other information or sugestions. 
If you need me to do something to help you understand the problem better let me
know. 


Reproducible: Always

Steps to Reproduce:
1. Launch the application
2.
3.

Actual Results:  
[redmage@192 mozilla]$ ./mozilla
LoadPlugin: failed to initialize shared library
/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so
[/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so: undefined symbol:
_ZN16nsServiceManager23GetGlobalServiceManagerEPP17nsIServiceManager]
LoadPlugin: failed to initialize shared library
/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so
[/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so: undefined symbol:
_ZN16nsServiceManager23GetGlobalServiceManagerEPP17nsIServiceManager]
[redmage@192 mozilla]$


Expected Results:  
loaded the plug-in 

I suspect the install of the JRE. The JRE I'm running is 

Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01)
Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode)

I'm not sure if I installed it correctly
However everything else that is dependant on this java installation works as
expected e.g. Java Web Start.
-> Oji

which gcc version do you see in "about:buildconfig" (as URL) ?
if gcc 3.2 : follow the plugindoc link in about:plugins to find the correct plugin

[/usr/local/j2re1.4.1/plugin/i386/mozilla/javaplugin_oji.so: undefined symbol:
_ZN16nsServiceManager23GetGlobalServiceManagerEPP17nsIServiceManager]

This looks like you have a gcc3.2 compiled Mozilla but the JRE is compiled with
GCC2.95 (you need a gcc3.2 compiled JRE)

Assignee: ashuk → joshua.xia
Component: Java APIs for DOM → OJI
QA Contact: avm → dsirnapalli
If comment #2 is right, this bug can be considered as invalid :

Just see here for more infos :

http://plugindoc.mozdev.org/whichjava.html
you can also build mozilla by using gcc 2.9x or use jre1.4.2 's jpi that built
by gcc3.x 
same problem here with rc2.

Java Plugin worked fine with rc1. If I install rc2 (both binary from
ftp.mozilla.org under SuSE 8.2) I will get

LoadPlugin: failed to initialize shared library
/opt/jre1.3.1_08/plugin/i386/ns600/libjavaplugin_oji.so
[/opt/jre1.3.1_08/plugin/i386/ns600/libjavaplugin_oji.so: undefined symbol:
__vt_17nsGetServiceByCID]

Doesn't matter if I user Sun Java 1.3.1 or 1.4.1 or blackdown java - same problem.

Is rc2 (binary from ftp.mozilla.org) compiled with another gcc?
Sorry, rc2 (from ftp.mozilla.org) is really build with another gcc.

So another blackdown java works fine.
LoadPlugin: failed to initialize shared library
/usr/local/mozilla/plugins/java2/plugin/i386/ns600/libjavaplugin_oji.so
[/usr/local/mozilla/plugins/java2/plugin/i386/ns600/libjavaplugin_oji.so:
undefined symbol: __vt_17nsGetServiceByCID]
-> invalid

Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
*** Bug 211019 has been marked as a duplicate of this bug. ***
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.