KDE4.1 & Seamonkey Issue

[Mumia W.]

On 08/08/2008 01:24 PM, Leonard Chatagnier wrote:
> --- "Mumia W."
> <paduille.4062.mumia.w+nospam at earthlink.net> wrote:
> 
>> On 08/07/2008 01:29 AM, Leonard Chatagnier wrote:
>>> --- "Mumia W."
>>> <paduille.4062.mumia.w+nospam at earthlink.net>
>> wrote:
>>>> On 08/06/2008 04: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):
>>>>> [...]
>>>> Your Seamonkey outputs far more errors than mine;
>>>> however, I'm using the 
>>>> 32-bit Seamonkey from Mozilla.org. I was
>> surprised
>>>> to see you say that 
>>>> you can run Seamonkey from the CLI even after you
>>>> get an error loading 
>>>> libxul.so which is critical to Mozilla
>> applications.
>>>> Examine the file ~/.xsession-errors to see if
>>>> Seamonkey leaves any 
>>>> useful error messages as it fails to load.
>>> Didn't find seamonkey in there but it had a lot of
>>> enties.  The file is attached as err.txt just in
>> case
>>> you want to take a look.  Appreciate the
>> suggestion
>>> and trying to help.
>>>
>>>
>>> Leonard Chatagnier
>>> lenc5570 at sbcglobal.net
>>>
>> Log in through a virtual console and start X like
>> so:
>>
>> startx > err2.txt 2>&1
>>
>> Then start Seamonkey and see if any error messages
>> appear. Also, try to 
>> find out what the Seamonkey icon in the panel is
>> trying to launch; the 
>> path to the program might be wrong.
>>
> Not sure i did this as you wanted. I logged out of
> kde4.1 and selected console log in, typed the above
> after logging in which got me back to kde4.1, then
> opened konsole and retyped the above followed by
> seamonkey on a new prompt and the output is:
> 
> lchata 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 ordirectory]
> ERROR: ld.so: object '/usr/lib/libartsdsp.so.0' from
> LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object '/usr/lib/libartsc.so.0' from
> LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object '/usr/lib/libartsdsp.so.0' from
> LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object '/usr/lib/libartsc.so.0' from
> LD_PRELOAD cannot be preloaded: ignored.
> 
> Hope this is what your seeking if not please explain
> what you mean by "virtual console".
> And Thanks,
> 
> 
> Leonard Chatagnier
> lenc5570 at sbcglobal.net
> 

Did Seamonkey launch when you did this?

Show us the output of these commands:

which seamonkey
dpkg -l seamonkey

Your path seems set up so that Seamonkey should launch when you click 
the panel icon. Make sure the command used by the panel icon is simply 
"seamonkey".