Closed Bug 764461 Opened 12 years ago Closed 12 years ago

SM 2.10 does not start due to libxul.so: cannot open shared object file: No such file or directory

Categories

(SeaMonkey :: General, defect)

SeaMonkey 2.10 Branch
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 762621

People

(Reporter: long, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10
Build ID: 20120604225847

Steps to reproduce:

Downloaded seamonkey 2.10 on Fedora 17 x86_64.  Unpacked it to /usr/local/.  Ran /usr/local/seamonkey/seamonkey


Actual results:

[long@raptor seamonkey]$ /usr/local/seamonkey/seamonkey
XPCOMGlueLoad error for file /usr/local/seamonkey/libxpcom.so:
libxul.so: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
[long@raptor seamonkey]$ 



Expected results:

Seamonkey should start
Forgot to mention that:

[long@raptor ~]$ LD_LIBRARY_PATH=/usr/local/seamonkey /usr/local/seamonkey/seamonkey

does work.
Now I've discovered that once I installed the fedora nspluginwrapper RPM the problem goes away.  That installed a whole pile of dependencies so I don't know what here was actually causing the problem:

Installed:
  nspluginwrapper.i686 0:1.4.4-9.fc17                                                                          

Dependency Installed:
  cyrus-sasl-lib.i686 0:2.1.23-29.fc17  libcurl.i686 0:7.24.0-2.fc17   libdb.i686 0:5.2.36-5.fc17              
  libidn.i686 0:1.24-1.fc17             libssh2.i686 0:1.4.1-2.fc17    ncurses-libs.i686 0:5.9-4.20120204.fc17 
  nspr.i686 0:4.9-2.fc17                nss.i686 0:3.13.4-3.fc17       nss-softokn.i686 0:3.13.4-2.fc17        
  nss-util.i686 0:3.13.4-2.fc17         openldap.i686 0:2.4.31-2.fc17  openssl.i686 1:1.0.0j-1.fc17            
  readline.i686 0:6.2-4.fc17            sqlite.i686 0:3.7.11-3.fc17
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.