$ ldd hadsm3_se_5.10_x86_64-pc-linux-gnu
	linux-gate.so.1 =>  (0xffffe000)
	libm.so.6 => /lib32/libm.so.6 (0xf7f1b000)
	libpthread.so.0 => /lib32/libpthread.so.0 (0xf7f03000)
	libc.so.6 => /lib32/libc.so.6 (0xf7db3000)
	/lib/ld-linux.so.2 (0xf7f54000)

$ ldd hadsm3_um_5.10_x86_64-pc-linux-gnu
	linux-gate.so.1 =>  (0xffffe000)
	libm.so.6 => /lib32/libm.so.6 (0xf7f1a000)
	libpthread.so.0 => /lib32/libpthread.so.0 (0xf7f02000)
	libc.so.6 => /lib32/libc.so.6 (0xf7db2000)
	/lib/ld-linux.so.2 (0xf7f53000)

Peter-Frank, I\'m not a Linux user, but does this help? It\'s about the same exit code that all your crashed models have had.

http://boincfaq.mundayweb.com/index.php?language=1&view=280&sessionID=f376631125417463e3fa11d7cf268081

$ pwd
/var/lib/boinc-client/projects/climateprediction.net

$ ls -la
total 212
drwxrwx--x 2 boinc boinc  4096 2008-03-31 17:57 .
drwxrwx--x 4 boinc boinc  4096 2008-03-31 17:56 ..
-rw-r--r-- 1 boinc boinc  3782 2008-03-31 17:57 hadcm3_40.png
-rw-r--r-- 1 boinc boinc 13708 2008-03-31 17:57 hadcm3_banner_290.png
-rw-r--r-- 1 boinc boinc 49890 2008-03-31 17:57 hadcm3_ss_290_1.png
-rw-r--r-- 1 boinc boinc 48077 2008-03-31 17:57 hadcm3_ss_290_2.png
-rw-r--r-- 1 boinc boinc 41929 2008-03-31 17:57 hadcm3_ss_290_3.png
-rw-r--r-- 1 boinc boinc    76 2008-03-31 17:57 slideshow_hadcm3_00
-rw-r--r-- 1 boinc boinc    74 2008-03-31 17:57 slideshow_hadcm3_01
-rw-r--r-- 1 boinc boinc    74 2008-03-31 17:57 slideshow_hadcm3_02
-rw-r--r-- 1 boinc boinc    74 2008-03-31 17:57 slideshow_hadcm3_03
-rw-r--r-- 1 boinc boinc    76 2008-03-31 17:57 slideshow_hadcm3i_00
-rw-r--r-- 1 boinc boinc    74 2008-03-31 17:57 slideshow_hadcm3i_01
-rw-r--r-- 1 boinc boinc    74 2008-03-31 17:57 slideshow_hadcm3i_02
-rw-r--r-- 1 boinc boinc    74 2008-03-31 17:57 slideshow_hadcm3i_03
-rw-r--r-- 1 boinc boinc    68 2008-03-31 17:57 stat_icon

If you look in my signature, you\'ll find \'readme posts\' in blue. If you click on that link, and then click on \'readme - crashes and other problems\', you should find a list of posts organised by category. One of the categories is \'linux\', and the two entries near the bottom of that category refer to 32-bit library support.

Each major distribution seems to use different terminology, and there is often more than one way of doing the same thing, so you may need to use your distribution\'s forums or support-database-search in order to find the solution if your distribution is not mentioned.

Sounds like a priviledges problem.
If it\'s installed under user root, then only user root can run it, to be able to have write access.

It should be installed under a \'normal\' user.