seamonkey 2.0.13 does not start, missing libxpcom.so and libxpcom_core.so (Natty, x86_64)

Bug #759406 reported by Wladimir Mutel
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
seamonkey (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: seamonkey

$ seamonkey
/usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin: symbol lookup error: /usr/lib/seamonkey-2.0.13/components/libsuite.so: undefined symbol: NS_GetServiceManager

$ ldd /usr/lib/seamonkey-2.0.13/components/libsuite.so
        linux-vdso.so.1 => (0x00007fff862d3000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f00bdd23000)
        libxpcom.so => not found
        libxpcom_core.so => not found
        libplc4.so => /usr/lib/libplc4.so (0x00007f00bdb1d000)
        libnspr4.so => /usr/lib/libnspr4.so (0x00007f00bd8e2000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f00bd5db000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f00bd247000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f00be1c5000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f00bd043000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f00bcdbd000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f00bcba7000)

Revision history for this message
Wladimir Mutel (mwg) wrote :

Also tried this :

$ sudo rm /usr/lib/seamonkey-2.0.13/components/libsuite.so

$ seamonkey
/usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin: symbol lookup error: /usr/lib/seamonkey-2.0.13/components/libdbusservice.so: undefined symbol: NS_Alloc

$ ldd /usr/lib/seamonkey-2.0.13/components/libdbusservice.so
        linux-vdso.so.1 => (0x00007fffe17ff000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f60fa8d0000)
        libxpcom.so => not found
        libnspr4.so => /usr/lib/libnspr4.so (0x00007f60fa694000)
        libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x00007f60fa46e000)
        libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f60fa22a000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f60f9f23000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f60f9b8f000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f60fad18000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f60f998b000)
        libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f60f9739000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f60f944a000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f60f9242000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f60f8fbc000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f60f8da6000)
        libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007f60f8ba1000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f60f8964000)

Revision history for this message
Wladimir Mutel (mwg) wrote :

removed also /usr/lib/seamonkey-2.0.13/components/libdbusservice.so
then seamonkey started seemingly fine, but crashed in libspellchecker.so very soon
removed /usr/lib/seamonkey-2.0.13/components/libspellchecker.so , and seamonkey works more stable afterwards (including Mail&NewsGroups)

But for Ubuntu package, these manual interventions are IMO undesirable anyway.

Revision history for this message
Micah Gersten (micahg) wrote :

Thank you for reporting this to Ubuntu. This works fine for me on Natty 64 bit. Could you please try reinstalling the package? I don't see anything obviously wrong based on the output provided. If you're still having an issue, could you please provide the output of:
ldd /usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin

Also, please make sure that 'which seamonkey' shows /usr/bin/seamonkey and not another one.

Changed in seamonkey (Ubuntu):
status: New → Incomplete
Revision history for this message
Vogon Zarniwoop (vogonzarniwoop) wrote :

I'm seeing this as well, under the latest Natty updates as of 16-Apr-2011.

$ uname -a
Linux io 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

$ seamonkey
/usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin: symbol lookup error: /usr/lib/seamonkey-2.0.13/components/libsuite.so: undefined symbol: NS_GetServiceManager

This was a new install on a new machine, so there isn't any prior config files hanging around.

Curiously, the --version option doesn't have this problem, and correctly report the version string:

$ seamonkey --version
Mozilla SeaMonkey 2.0.13, Copyright (c) 1998-2010 mozilla.org

Other things:

$ which seamonkey
/usr/bin/seamonkey

$ ldd /usr/lib/seamonkey-2.0.13/seamonkey-2.0-bin
        linux-vdso.so.1 => (0x00007ffffdfff000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd66b907000)
        libxul.so => not found
        libxpcom_core.so => not found
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd66b572000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fd66bb4b000)

Revision history for this message
Jason Joines (joines) wrote :

Same problem as of latest Natty right now.

Revision history for this message
yen rio (yenrio) wrote :

Same problem in Kubuntu after latest Natty updates

Revision history for this message
Ed Swierk (eswierk) wrote :

The fact that ldd /usr/lib/seamonkey-2.0.13/components/libsuite.so can't find libxpcom.so is a red herring; that library lives in /usr/lib/seamonkey-2.0.13 which isn't in the normal library path, and ldd shows the same result even on a system where seamonkey is working.

I ran LD_DEBUG=all seamonkey and captured the output (see attachment). It shows NS_GetServiceManager is found in libxpcom.so when libimgicon.so is loaded, but for some reason when libsuite.so is loaded, libxpcom.so is never even searched.

Changed in seamonkey (Ubuntu):
status: Incomplete → New
Revision history for this message
keith burnett (ping-keith-gmail) wrote :

Same problem in Xubuntu; have checked this morning after updates, and Seamonkey still not launching windows when clicking on menu entry.

My workround is to use the 2.0.14 binary package from mozilla for now with a manual .desktop file in ~/.local/share

Revision history for this message
Andrej (rarog) wrote :

Same here with Kubuntu 11.04 (x64) but I think the problem is universal and independent from Ubuntu flavour.

Revision history for this message
Antoine Wils (antoine-wils) wrote :

I have same config as Vogon Zarniwoop and had an issue with libxpcom.so but when using eclipse.
I manage to fix it. See my post at https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/749698

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers