Getting Java working

Daniel

unread,

Apr 19, 2013, 6:19:40 AM4/19/13

to

The release notes foe SM 2.18b2 includes this para for Linux installs:-

The Oracle Java 7 plugin does not work with SeaMonkey (bug 754622).
Workaround: Remove pluginreg.dat from your profile, then start SeaMonkey
with LD_PRELOAD=libstdc++.so.6 in front.

I expect I can blowaway the pluginrec.dat file from the profile, but,
being a "point and double click" type person, how do I achieve the
LD_PRELOAD stuff??

Should this be added to the desktop icons properties??

And will I have to do this each time I install a new beta version??

In blowing away the pluginrec.dat file, will I also lose the other
plugins/extensions/etc that I have installed??

TIA

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022820

or

User agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:20.0)
Gecko/20100101 Firefox/20.0 SeaMonkey/2.17 Build identifier: 20130320191715

Jens Hatlak

unread,

Apr 19, 2013, 4:07:21 PM4/19/13

to

Daniel wrote:
> The release notes foe SM 2.18b2 includes this para for Linux installs:-
>
> The Oracle Java 7 plugin does not work with SeaMonkey (bug 754622).
> Workaround: Remove pluginreg.dat from your profile, then start SeaMonkey
> with LD_PRELOAD=libstdc++.so.6 in front.
>
> I expect I can blowaway the pluginrec.dat file from the profile, but,
> being a "point and double click" type person, how do I achieve the
> LD_PRELOAD stuff??
>
> Should this be added to the desktop icons properties??

You can try that. If it doesn't work, you can write a wrapper script,
like so:

#!/bin/bash
exec LD_PRELOAD=libstdc++.so.6 /path/to/your/seamonkey $@

name it "seamonkey-java-workaround" or something, make it executable
(chmod +x) and call it instead of the original. [Be sure that the file
uses Unix line ends. Linux editors would do that by default.]

> And will I have to do this each time I install a new beta version??

No, at least not if you always use the wrapper script (or icon, if it
works). However if you call SM without the workaround once, you'll have
to remove pluginreg.dat once again.

> In blowing away the pluginrec.dat file, will I also lose the other
> plugins/extensions/etc that I have installed??

No. First of all, pluginreg.dat only concerns plugins, not extensions
(add-ons). Second, the file will be recreated automatically and filled
with information for all plugins SM can find. It's just that if the
LD_PRELOAD workaround is not applied, the Java plugin is not detected
correctly and a broken record is added to pluginreg.dat.

HTH

Jens

--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>

Daniel

unread,

Apr 20, 2013, 6:23:07 AM4/20/13

to

Thanks very much for this detailed response, Jens. I'll let you know
*when* I stuff it up!!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022820

or

User agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:21.0)
Gecko/20100101 Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022815

Daniel

unread,

Apr 21, 2013, 6:56:16 AM4/21/13

to

Nearly mucked up .... had drafted a response to above because nothing
had changed, but then I realised that I hadn't removed the pluginreg.dat
from the profile, so will do that and give it another try.

Daniel

unread,

Apr 22, 2013, 8:12:52 AM4/22/13

to

Jens, tonight I remembered (just) to re-name my pluginreg.dat file (to
pluginreg.dat.old) before I double-clicked on my executable file
(SeaMonkey.sh), but then nothing happened, as far as I could tell ... I
still had to double click on my seamonkey file to start SM.

Jens, in the exec LD_PRELOAD=libstdc++.so.6 /path/to/your/seamonkey $@
line of the script you gave above is the seamonkey the seamonkey program
file or the directory in which the seamonkey program is installed??

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022820

or

User agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:21.0)
Gecko/20100101 Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022815

Jens Hatlak

unread,

Apr 22, 2013, 12:48:45 PM4/22/13

to

Daniel wrote:
> Jens, in the exec LD_PRELOAD=libstdc++.so.6 /path/to/your/seamonkey $@
> line of the script you gave above is the seamonkey the seamonkey program
> file or the directory in which the seamonkey program is installed??

The executable (or an executable script).

Daniel

unread,

Apr 23, 2013, 5:25:09 AM4/23/13

to

Jens Hatlak wrote:
> Daniel wrote:
>> Jens, in the exec LD_PRELOAD=libstdc++.so.6 /path/to/your/seamonkey $@
>> line of the script you gave above is the seamonkey the seamonkey program
>> file or the directory in which the seamonkey program is installed??
>
> The executable (or an executable script).
>
> HTH
>
> Jens

O.K., so that line ends in ..../seamonkey/seamonkey!! That's what I
thought, but thanks for confirming.

I've lost the script that I have to run to get onto the internet (hence
my being on Win7 tonight!) so am unable to check further just at the
moment, but "I'll be back!!"

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101

Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130418192405