As long as this is going to keep on going, some more:

There's mostly 2 libraries involved in the problem, one for the program, and the other for the graphics. They have so.62 in the name, and these are old versions. The current ones are 8.
The old ones are being used for backwards compatibility with a few old OS versions. I think that 2 are CentOS and openSUSE.

If you watch the loooong list during installing the 32 bit libs, you can see the "6" versions get installed, and then latter, during clean up, get removed, because there's a newer version.

So one solution that would make things a lot easier for some, would be to drop these older versions, and use so.8 versions of all of the libs.
It depends on the ratio of the current complainees, to that of the new lot of complainees, which would cause less posts here.

I had to reinstall my operating system a couple of days ago, after replacing a failed SSD. I didn't have the option of copying the 32-bit file "/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16" from my other desktop computer this time.

I came to a previous post in this thread, which points to this webpage, and:

1. Tried

sudo apt-get install ia32-libs libstdc++6 libstdc++5 freeglut3

2. but found that

Package ia32-libs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
lib32z1 lib32ncurses5 lib32bz2-1.0

so

sudo apt-get install lib32z1 lib32ncurses5 lib32bz2-1.0

3. Then I finished installing the remaining libraries

sudo apt-get install libstdc++6 libstdc++5 freeglut3

I found that a number of climateprediction.net tasks have downloaded overnight, and are

Running

at around 10% Progress, so it seems that it is all working again.

Hooray!

A word of warning on SSDs for CPDN I managed to screw one up by exceeding the number of write cycles they will last for on too many blocks/sectors whatever. I am told the newer ones have bigger numbers for the write cycles and it was I think only a 64GB drive. If I replace the drive in my netbook with another SSD, it will be at least 256GB and I will only use one of the two cores. It took about 2 years for the drive to fail running 24/7 with only occasional breaks.

You can decide whether it is worth it with your cpu speed and size of hard disk.

Thanks for that Dave. I did have a problem previously and wanted to use the internal HDD instead of the SSD for BOINC (per my post of 20 January 2014 on BOINC site).

However the number of bad sectors was very low and I never managed to get BOINC to use my HDD, so I left it working on the SSD, and after reinstalling the operating system (due to other problems) on 25 April 2014, the number of bad sectors stopped increasing by about 3 every day, and peaked at 302 months before failing suddenly on 26 September 2014. It was at 304 when I checked it shortly before it failed.

The new SSD has been in for 5 days and it still has 0 bad sectors.

I think the thing that prevents BOINC from using the HDD is that the operating system doesn't want to mount the HDD at startup for some reason.

On my main machine, I have BOINC running in it's own directory, /home/BOINC/

Previously I had run it under /home/dave/BOINC but several people have told me that this is not a good practice for security reasons. I suspect the risk is still pretty low but I have gone down this route rather than using the packaged version on my machine.

After somehow breaking my Kubuntu upgrade to 14.10 I have done a clean install and

sudo apt-get install lib32z1 lib32ncurses5 lib32bz2-1.0 lib32stdc++6

seems to have grabbed everything I needed.

I'm having the same problem after upgrading Ubuntu recently from an old 9.04 (which was running CPDN perfectly with the relevant libs) through various iterations to 14.04 now. It seems to be the libstdc++6 (lib32stdc++6?) that is my problem, all the others are now installed. I have now located the libstdc file but still have to install it but haven't found lib32stdc++6. I was thinking of downloading a 32 bit version of 14.04 and running it as a liveCD to see if the file is there, then moving it over to somewhere I can access it and installing it from there.

---

Ok, and a few more 32bit libs to get the graphics going again.