129181 - Fails to start if IBM Java2 plugin installed

Status: VERIFIED FIXED

(Core Graveyard :: Plug-ins, defect)

Description

[Ludovic Brenta]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8+) Gecko/20020227
BuildID:    2002022700

Mozilla fails to start when the Java2 plugin from IBM Development Kit is
symlinked into /usr/lib/mozilla/plugins.

Reproducible: Always
Steps to Reproduce:
1. Install the IBM Development Kit (IBMJava2-SDK-1.3-10.0.i386.rpm) from www.ibm.com
2. Symlink /opt/IBMJava2-13/jre/bin/libjavaplugin_oji.so into
/usr/lib/mozilla/plugins
3. Restart mozilla.

Actual Results:  mozilla does not actually crash; it starts 5 processes but does
not open any window. I have to kill mozilla from top or gtop.

If I remove the symlink from /usr/lib/mozilla/plugins, mozilla starts properly
again.

Expected Results:  mozilla should show up.  The about:plugins page should show
the Java2 plugin.  Applets should execute.

I have a RedHat 7.2 with kernel 2.4.9-13smp.

The above incorrect behaviour also occurs if I try the netscape 4 plugin,
/opt/IBMJava2-13/jre/bin/javaplugin.so.

I deinstalled and reinstalled mozilla and the JDK using RPM, and even upgraded
to the latest nightly build of mozilla (I was using 0.9.8 release). I also tried
running mozilla as root and as a regular user. Same thing.

Comment 1

[John Levon]

Can you try again with a current Mozilla build please ?

Comment 2

[anthonyd]

reporter,

any luck in reproducing this with a current build?

anthonyd

Comment 3

[Ludovic Brenta]

Sorry for the late reply.  I tried again with Mozilla 0.9.9 (release) and a
sligtly newer version of IBM's JDK (the old one was no longer on their web
site).  It now works as expected.  Unfortunately I cannot say whether the change
came from IBM or Mozilla.

The following combination of RPMS work for me:
IBMJava2-SDK-1.3-13.0.i386.rpm
mozilla-0.9.9-0.i386.rpm
mozilla-mail-0.9.9-0.i386.rpm
mozilla-nspr-0.9.9-0.i386.rpm
mozilla-nss-0.9.9-0.i386.rpm
mozilla-psm-0.9.9-0.i386.rpm

Resolving bug, changing status to FIXED (pretending that the bug was in Mozilla
and was fixed, which is not confirmed)

--
Ludo.

Comment 4

[shrirang khanzode]

.