KDE4.1 & Seamonkey Issue

[NoOp]

On 08/06/2008 04:40 PM, Leonard Chatagnier wrote:
> --- NoOp <glgxg at sbcglobal.net> wrote:
> 
>> On 08/06/2008 02:17 PM, Leonard Chatagnier wrote:
>> > Am using hardy x86-64, KDE4.1 and can only start
>> > Seamonkey from the cli interface(Konsole).  When I
>> try
>> > to start Seamonkey from the K menu or a seamonkey
>> icon
>> > in the panel, it will do the busy cursor routine
>> for
>> > some time then just disappear. No problem running
>> > firefox or opera from menu or icon, just
>> seamonkey. 
>> > Seamonkey runs ok from cli but outputs errors
>> shown
>> > below(can anyone offer a fix or link that would
>> help):
>> > 
>> > TIA,
>> > 
>> >  chata at ubuntu-hardy-64bit:~$ seamonkey 
>> > LoadPlugin: failed to initialize shared library
>> >
>>
> /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/gcjwebplugin.so
>> > [libxul.so: cannot open shared object file: No
>> such
>> > file or directory]   
>> 
>> Do you have Icedtea installed?
>>
> http://packages.ubuntu.com/hardy/icedtea-gcjwebplugin
>> 
> Yes.
> lchata at ubuntu-hardy-64bit:/usr/share/seamonkey/defaults/autoconfig$
> aptitude show icedtea-gcjwebplugin
> Package: icedtea-gcjwebplugin
> State: installed
> Automatically installed: yes
> Version: 1.0-0ubuntu7
> Priority: extra
> Section: universe/web
> Maintainer: Matthias Klose <doko at ubuntu.com>
> Uncompressed Size: 213k
> Depends: libatk1.0-0 (>= 1.20.0), libc6 (>= 2.2.5),
> libcairo2 (>= 1.6.0), libgcc1, libglib2.0-0 (>=
> 2.12.0), libgtk2.0-0 (>= 2.12.0), libnspr4-0d,
> libpango1.0-0 (>=
>          1.20.1), libstdc++6 (>= 4.1.1-21),
> openjdk-6-jre (>= 6b06), xulrunner-1.9
> Description: Java plugin based on IcedTea and
> gcjwebplugin
>  icedtea-gcjwebplugin is a little web browser plugin
> to execute Java applets. It is targeted for Mozilla
> and compatible browsers that support the NPAPI.
> 
>> How did you install SeaMonkey?
>> 
> Used synaptic. Had some crazy inter-dependency with
> iceape and ended up removing iceape(automatic?) before
> could install seamonkey.

Unfortunately (or fortunately depending on how you look at it) I do not
have any 64bit systems to test on. Can you try with a new SM profile:

seamonkey -P

and then create a new profile. This will eliminate any possible issues
that may have occured on the default install profile.

Also:
http://packages.ubuntu.com/source/hardy/seamonkey
You might want to do a complete reinstall given that you are early into
this:

sudo apt-get remove --purge seamonkey
sudo apt-get install seamonkey