Closed
Bug 444687
Opened 17 years ago
Closed 17 years ago
libxpcom.so - no such file or directory
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: epp, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
Upon running the Linux installer of the release candidate of SM 1.1.11, the following error appeared:
Fatal error [-618]. Couldn't open xpistub library: libxpcom.so. Cannot open shared object file: No such file or directory.
seamonkey-1.1.11.en-US.linux-i686.installer.tar.gz dated July 3, 2008 01:54
Reproducible: Always
Steps to Reproduce:
1.Download 1.1.11 release candidate installer
2.Unpack, then run installer, set up installation and directory
3.Click Install
Actual Results:
Fatal error occurred.
Expected Results:
SM should install without error. A file is missing.
After deleting all relevant directories, I tried to reinstall 1.1.10 using its installer file, which up to now had worked perfectly.
Upon running the 1.1.10 installer, the same error outlined above, also occurred.
The only way to install 1.1.11 successfully was to download the tar.gz file dated July 6, 2008, instead of using the installer.
![]() |
||
Comment 1•17 years ago
|
||
We have not changed the 1.1.10 file, so have you changed something in your system between the successful and unsuccessful tries to install it?
(In reply to comment #1)
> We have not changed the 1.1.10 file, so have you changed something in your
> system between the successful and unsuccessful tries to install it?
Nothing was changed.
I have always installed it in my /home directory. When a new version is released, I simply delete both the seamonkey and seamonkey-installer sub-directories with their files, delete them from Trash, then unpack the installer tar.gz and subsequently run the installer. Up until now, there were no problems at all using the Linux installer files.
The 1.1.10 installer file was the same file downloaded a couple of weeks back when it was released. This is why I do not understand getting the same error with the installers from both versions, the 1.1.10 installer ran perfectly prior to this.
![]() |
||
Comment 3•17 years ago
|
||
It's very strange if you suddenly get this failure with the same installer that has already worked on your system. Something needs to be different there.
I know that a number of people have successfully installed 1.1.11 candidates from the installer, esp. during the time when we had a broken non-installer tar.gz out there.
ajschult, do you have any idea what could be happening there?
Comment 4•17 years ago
|
||
no. The installer extracts xpcom.xpi to a temporary directory and then tries to dynamically load it from there. For whatever reason, it can't find libxpcom.so when it tries to dynamically load it. I mentioned some wild guesses on what sorts of things could cause this, but tracking this down would be hard. The temporary directory would be something like /tmp/xpi.ABCDEF, but it only gets created after you press "Install" and it gets deleted once the installer is done (it should exist while the error dialog is up). If the file is there (which wouldn't surprise me) then the issue is why the installer isn't looking in that directory.
Updated•17 years ago
|
Component: Build Config → Installer
QA Contact: build-config → general
On these two desktop systems tonight:
Intel Pentium/MMX (166 MHz, 262 Mb RAM)
AMD K6-2 with 3-D Now (500 MHz, 524Mb RAM)
The 1.1.11 installer worked perfectly the first time.
The ThinkPad T43 laptop: Intel Pentium M (1.86 GHz, 1.536Gb RAM), is where the error occurred. Given that the speed of this is far superior to the other two systems, I would not have expected something like this to occur.
I will repeat the process on the ThinkPad again and will report back with the results.
I downloaded a new copy of the installer file and repeated the process on the ThinkPad. 1.1.11 installed successfully.
Comment 7•17 years ago
|
||
So, it was a corrupted download.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•