Seamonkey 2.1/2.2 breaking Java plugin support on Centos 5 Linux?

I'm a long-time user of Seamonkey, from since it was called Mozilla.
The  recent 2.1 and 2.2 updates seem to have broken Java support on my  Centos 
5.5 box (32 bits) and I really can't figure this out.
Seamonkey is installed in /usr/local.
Starting  from 2.1, the /usr/local/seamonkey/plugins directory is gone. As per  
the release notes, plugins are now managed on a per-user basis in  
$HOME/.mozilla/plugins
So far, so good. I used to have a link in  /usr/local/seamonkey/plugins pointing 
to  /usr/local/jre1.6.0_12/plugin/i386/ns7/libjavaplugin_oji.so (I install  
Sun's JREs in /usr/local too... it shows my BSD background I guess  )
So I moved that link to $HOME/.mozilla/plugins but now about :plugins doesn't 
show any Java plugin detected.
Worse, $HOME/.mozilla/seamonkey/<profile name>.default/pluginreg.dat shows that 
the plugin is rejected. It contains:
[INVALID]
/usr/local/jre1.6.0_12/plugin/i386/ns7/libjavaplugin_oji.so:$
1232187965000:$
I've tried with the "new" plugin found in 
/usr/local/jre1.6.0_12/lib/i386/libnpjp2.so too. Doesn't work either.
I  vaguely suspect that there might be a shared library issue with the  newest 
Seamonkey binaries and Centos 5.5, but then every other plugin  works OK, 
including Flash, Acrobat and all. So what's the issue with the Java  plugin? 
There's no error when I start Seamonkey from a terminal window.
Any help greatly appreciated, I must not be the only Seamonkey user on Centos 
5.5, or so I hope 
Thanks for your time,
_Alain_
0
Alain
7/11/2011 5:32:06 PM
📁 mozilla.support.seamonkey
📃 13721 articles.
⭐ 0 followers.

💬 3 Replies
👁️‍🗨️ 1587 Views


On 12/07/2011 01:32, Alain Alain wrote:
> I'm a long-time user of Seamonkey, from since it was called Mozilla.
> The  recent 2.1 and 2.2 updates seem to have broken Java support on my  Centos 
> 5.5 box (32 bits) and I really can't figure this out.
> Seamonkey is installed in /usr/local.
> Starting  from 2.1, the /usr/local/seamonkey/plugins directory is gone. As per  
> the release notes, plugins are now managed on a per-user basis in  
> $HOME/.mozilla/plugins
> So far, so good. I used to have a link in  /usr/local/seamonkey/plugins pointing 
> 
> to  /usr/local/jre1.6.0_12/plugin/i386/ns7/libjavaplugin_oji.so (I install  
> Sun's JREs in /usr/local too... it shows my BSD background I guess  )
> So I moved that link to $HOME/.mozilla/plugins but now about :plugins doesn't 
> show any Java plugin detected.
> Worse, $HOME/.mozilla/seamonkey/<profile name>.default/pluginreg.dat shows that 
> the plugin is rejected. It contains:
> [INVALID]
> /usr/local/jre1.6.0_12/plugin/i386/ns7/libjavaplugin_oji.so:$
> 1232187965000:$
> 
> I've tried with the "new" plugin found in 
> /usr/local/jre1.6.0_12/lib/i386/libnpjp2.so too. Doesn't work either.
> 
> I  vaguely suspect that there might be a shared library issue with the  newest 
> Seamonkey binaries and Centos 5.5, but then every other plugin  works OK, 
> including Flash, Acrobat and all. So what's the issue with the Java  plugin? 
> There's no error when I start Seamonkey from a terminal window.
> 
> Any help greatly appreciated, I must not be the only Seamonkey user on Centos 
> 5.5, or so I hope 
> 
> Thanks for your time,
> _Alain_
Gecko dropped support for the OJI plugin. Don't know why the newer NPAPI
plugin doesn't work. Perhaps it's a 32 vs 64 bit issue or a path issue.
Phil
-- 
Philip Chee <philip@aleytys.pc.my>, <philip.chee@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
0
Philip
7/11/2011 5:46:17 PM
Alain Alain wrote:
> I'm a long-time user of Seamonkey, from since it was called Mozilla.
> The  recent 2.1 and 2.2 updates seem to have broken Java support on my  Centos
> 5.5 box (32 bits) and I really can't figure this out.
> Seamonkey is installed in /usr/local.
> Starting  from 2.1, the /usr/local/seamonkey/plugins directory is gone. As per
> the release notes, plugins are now managed on a per-user basis in
> $HOME/.mozilla/plugins
> So far, so good. I used to have a link in  /usr/local/seamonkey/plugins pointing
>
> to  /usr/local/jre1.6.0_12/plugin/i386/ns7/libjavaplugin_oji.so (I install
> Sun's JREs in /usr/local too... it shows my BSD background I guess  )
> So I moved that link to $HOME/.mozilla/plugins but now about :plugins doesn't
> show any Java plugin detected.
> Worse, $HOME/.mozilla/seamonkey/<profile name>.default/pluginreg.dat shows that
> the plugin is rejected. It contains:
> [INVALID]
> /usr/local/jre1.6.0_12/plugin/i386/ns7/libjavaplugin_oji.so:$
> 1232187965000:$
>
> I've tried with the "new" plugin found in
> /usr/local/jre1.6.0_12/lib/i386/libnpjp2.so too. Doesn't work either.
>
> I  vaguely suspect that there might be a shared library issue with the  newest
> Seamonkey binaries and Centos 5.5, but then every other plugin  works OK,
> including Flash, Acrobat and all. So what's the issue with the Java  plugin?
> There's no error when I start Seamonkey from a terminal window.
>
> Any help greatly appreciated, I must not be the only Seamonkey user on Centos
> 5.5, or so I hope
>
> Thanks for your time,
> _Alain_
I found a way to easily create a link to the java plugin.
Right-click on the file lbnpjp2.so and select create link, then I cut 
and past the link into .mozilla/plugins in my home folder on openSUSE.
The only difference is I have jdk1.6.0_26 installed in home and the path 
is jdk1.6.0_26/jre/lib/i386/libnpjp.so
At a loss if that is what you did and it's not working.
If you can, you really should update to Java version 1.6.0_26.
0
WLS
7/11/2011 5:50:36 PM
Phil and others, thanks for your replies,

----- Original Message ----
From: Philip Chee <philip.chee@gmail.com>
To: support-seamonkey@lists.mozilla.org
Sent: Mon, July 11, 2011 7:46:17 PM
Subject: Re: Seamonkey 2.1/2.2 breaking Java plugin support on Centos 5 Linux?
On 12/07/2011 01:32, Alain Alain wrote:
> I'm a long-time user of Seamonkey, from since it was called Mozilla.
> The  recent 2.1 and 2.2 updates seem to have broken Java support on my  Centos 
> 5.5 box (32 bits) and I really can't figure this out.
(...)
Gecko dropped support for the OJI plugin. Don't know why the newer NPAPI
plugin doesn't work. Perhaps it's a 32 vs 64 bit issue or a path issue.
---- End Original Message ----
OK, I've tried with the latest JRE and setting up a link to 
/usr/local/jre1.6.0_26/lib/i386/libnpjp2.so.
Doesn't work either, it comes up in an [INVALID] section in pluginreg.dat :-(
I'm in a fully 32-bit world here so I don't think that could be the problem 
unless the JRE is 64-bit only which I don't think it is.
Path issue? can you elaborate on this? do you mean the process' PATH environment 
variable or something else?
ldd /usr/local/jre1.6.0_26/lib/i386/libnpjp2.so shows no unresolved external 
reference so I don't think I need to tweak LD_LIBRARY_PATH either.
_Alain_
0
Alain
7/12/2011 8:31:13 AM
Reply: