Browsers Availability?

[NoOp]

On 06/18/2007 04:04 PM, NoOp wrote:

> 
> You are replying to the sig (after the -- ) - please reply only in the
> message portion of the post.  Your question:
> 
>> Seems that the seamonkey installer requires later versions of the
>> libs, etc, than installed of Feisty. If anyone with Feisty has
>> attempted to install Seamonkey, came up with this issue and solved
>> it, your input is needed. If anyone knows of a Feisty repository that
>> includes a seamonkey installation, please let me know what it is. I
>> have a Feisty Ubuntu live CD install with Kubuntu-desktop installed.
>> Happy to supply any needed info.  Thanks for your consideration.
> 
> Not at all. I have SeaMonkey on Dapper, Edgy, and Feisty. If you
> followed the instructions above SeaMonkey *should* have installed just
> fine.
> 
> "I have a Feisty Ubuntu live CD install with Kubuntu-desktop installed."
> I'm assuming that you have a fully installed kunbutu system... Have you
> updated the system since you installed from the live CD ala
> sudo apt-get update
> sudo apt-get upgrade
> ?
> 
> Regarding your link on Mozilla forums:
> 
> I have the following libstdc's installed"
> - libstdc++5 version 1:3.3.6-15ubuntu1
> - libstdc++6 version 4.1.2-0ubuntu4
> - libstdc++6-4.0-dev version 4.0.3-4
> - libstdc++6-4.1-dev version 4.1.2-0ubuntu4
> 
> usr/lib/debug/libstdc++.so.6.0.8 comes from the libstdc++6 package so
> that should be fine. Can you also install libstdc++5 (use Synaptic
> please) and see if that corrects your problem?
> 
> I have a Feisty test server that I will remove libstdc++5 from and leave
> libstdc++6, and then install SM to see if I can reproduce the error.
> 

I just tested by removing libstdc++5 and the SeaMonkey installer does
indeed require libstdc++5 and gives the same error as you experienced:

./seamonkey-installer-bin: error while loading shared libraries:
libstdc++.so.5: cannot open shared object file: No such file or directory

Installing libstdc++5 corrects the problem, so install it and you should
be fine. I'll file a bug over on mozilla.