FAHClient 7.1.52 fails to run on Ubuntu 10.04 LTS 64 bit

[infraredzeus]

Dear Folding Community,

I have just installed FAHClient 7.1.52 on my machine running Ubuntu 10.04 LTS 64 bit. Sadly, FAHClient fails to load seemingly due to a dependency issue that was not checked for by the package manager during installation. While attempting to load FAHClient via the terminal, the following error is returned:

user@machine:~$ FAHClient
FAHClient: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

Libssl is installed on my machine but unfortunately the default version of that library for Ubuntu 10.04 is 0.9.8 . I believe that libssl 1.0.0 is only installed by default on the newest Ubuntu Release, 11.10 . I don't know how to work around this issue as I don't know how to update libssl without breaking packages and compatibility for essential system components. I assume that this problem may affect everyone using the current Long Term Support release of Ubuntu.

Does anyone know how I can work around this compatibility issue without breaking compatibility with other system components? Or should I simply wait for the next release for the newest client?

Here's a breakdown of some of my essential hardware:
Motherboard: Gigabyte M61P
CPU: AMD Athlon X2 4000+
GPU: NVIDIA 8600 GTS

Thanks in advance for your help,
infraredzeus

[jimerickson]

isn't this ticket number 791? wasn't this fixed in v7.1.44? at least thats how i read the change log. could be wrong though.

[infraredzeus]

It is similar to ticket number 971. The difference is that this problem affects different versions of libssl and FAHClient. Ticket 971 dealt with FAHClient v7.1.43 not being compatible with libssl v0.9.8 . The ticket was closed, but now FAHClient 7.1.52 no longer works with libssl v0.9.8, it expects libssl v1.0.0 which is not the default version in Ubuntu 10.04.

Here is the link to ticket 971: https://fah-web.stanford.edu/projects/FAHClient/ticket/791

[7im]

Joe needs to develop on, and include support for the newer versions of Linux, but needs to edit the .deb packages so the dependencies are still at the version level of the older linux versions.

A while back, I posted how to edit the .deb so I could remove the python 2.6 requirement and allow fah to install without error. I'm a newb and followed an article found with Google...

[arnold m]

I have the same problem when trying to run FAHCLient 7.1.52 on my amd64 system running under Debian 6.0 (Squeeze).
I would advise against editing .deb packages to "fix" dependencies. The recommended way to make a .deb package that will work on a certain version is to use a build environment with the tools and library from that same version. This build environment need not be a dedicated machine; a chroot is normally enough.

[7im]

You'd rather have 20 different client builds, one for each flavor and version of linux? Good luck supporting that...

[vitorgatti]

It seems someone compiled FAHClient with the same buggy dependencies from older versions of v7.
The bug returned, and I can confirm it.

I'm using Ubuntu 11.04 64bits and FAHClient won't run, asking for libssl.so.1.0.0, which doesn't exist.
I installed the package fahclient_7.1.52_amd64.deb

[DocJonz]

I've just installed Ubuntu 12.04 LTS beta on a test machine (to take a look at the new OS) and I've installed the v7 client (to have a play with the new F@H Client etc), and everything seems to be working swimmingly - might be worth a shot

[arnold m]

@7im: I'd rather not have the situation where I can install the package without warnings from my package manager, only to find out that the program in it will not run on my computer.

You may find mini-buildd useful to build packages for various flavours and versions of .deb-based Linux. I must admit it did cost me some some time to get it configured right when I set it up for personal use, though.
Supporting different builds takes time and resources, however if you edit the package to make it allow earlier versions, you ought to make sure the program really works with those earlier versions, which also takes time and resources.

[7im]

I have a dozen Linux VMs that I have been using to beta test V7.

The dependencies are a function of their build environment, not an actual requirement, IMO. The client has worked in every version so far, from Ubu 9.0 to 12 beta, even installed with -nodeps to get around the requirements. It was written in GTK to be compatible with Win, Lin, and OSX. It can't require too much specialized software, or it wouldn't work in all 3. The client is pretty generic, IMO.

Thanks for the recommendation about mini build. If it comes down to needing seperate builds, I'm sure Stanford will take a serious look at that.


NOTE: The manual install section (command line) of the V7 Linux (client) Install Guide shows how to install the clients while bypassing the build specific dependencies. Most versions of Linux have everything the fahclient needs to run, without needing an exact version of each library.

Linux V7 Manual Installation

Feedback is welcomed.

[Iced]

I have an AMD64 Ubuntu 10.04 LTS server as well.

I have been running "FAH6.02-Linux.tgz" for a number of years now and decided to try updating the client and have the same problem. I have tried installing 2 different ways:
- Just clicking on the .deb file that was downloaded from the Folding@Home page that brings up the package manager and installs. I thought it would be that easy
- Using command-line dpkg -i --force-depends as outlined on the Linux V7 Manual Build page

Between each method, I uninstalled all 3 components by:
dpkg -r fahclient; dpkg --purge fahclient
dpkg -r fahcontrol; dpkg --purge fahcontrol
dpkg -r fahviewer; dpkg --purge fahviewer

The unfortunate situation is having to support more than 1 version now - everything has not migrated from SSL 0.9.8 to 1.0.0 yet and poses a huge headache for those required to upgrade. Perhaps a solution to consider is to create 2 builds per release that use either 0.9.8 or 1.0.0 SSL? Support for multiple versions is already in place indirectly by recommending people install an previous version of the software. However, If a critical bug was ever encountered/exploited in the old versions that require a fix - either a patch build or recommending people upgrade to the latest which puts us in the same situation.

If still, the only option is to install an earlier version 'for now', at least specify on the installation page so others like me don't end up 'here' looking for 'why'. Thanks in advance.

[kwakubm]

It seems that version 7.1.43 works fine on Ubuntu 10.04. To install:

First, clean up other versions:

Code: Select all

sudo dpkg -r fahclient fahviewer
sudo dpkg --purge fahclient fahviewer

Then, download and install version 7.1.43. For 64-bit:

Code: Select all

wget --no-check-certificate https://fah-web.stanford.edu/file-releases/beta/release/fahclient/ubuntu-10.10-64bit/v7.1/fahclient_7.1.43_amd64.deb
wget --no-check-certificate https://fah-web.stanford.edu/file-releases/beta/release/fahviewer/ubuntu-10.10-64bit/v7.1/fahviewer_7.1.43_amd64.deb
sudo dpkg -i fahclient_7.1.43_amd64.deb
sudo apt-get install libglew1.5
sudo dpkg -i --force-depends fahviewer_7.1.43_amd64.deb

For 32-bit:

Code: Select all

wget --no-check-certificate https://fah-web.stanford.edu/file-releases/beta/release/fahclient/debian-sarge-32bit/v7.1/fahclient_7.1.43_i386.deb
wget --no-check-certificate https://fah-web.stanford.edu/file-releases/beta/release/fahviewer/debian-sarge-32bit/v7.1/fahviewer_7.1.43_i386.deb
sudo dpkg -i fahclient_7.1.43_i386.deb
sudo apt-get install libglew1.5
sudo dpkg -i --force-depends fahviewer_7.1.43_i386.deb