I'm running Slackware 13.37 64bit (XFCE 4.4 desktop) and having been running BOINC v 6.10.58 very smoothly for some time. Recently I tried the latest "recommended" version but am having some odd problems that I cannot seem to find any answer to.
My normal update method is to shut down the existing client, extract the new one in a separate folder, copy the new binaries to the existing folder and then restart the client. This has worked fine for until now.
With the current recommended version (6.12.34) up to and including 7.0.6, the client itself seems to work fine but the manager has a display issue where all the controls across the top of the page (File Edit View etc) display ok until the manager connects to the client but then they all contract to the far left such that only half of the File option control is visible. The Controls open using their Alt+foo hotkeys but there is no way to access them with the cursor or see them.
Since I don't see this problem coming up in any searches I've done I am guessing that I am missing a required display library or have the wrong version of one for these newer manager versions. Would it be possible to get a list of dependencies and/or what libs etc the manager was compiled against?
Any help would be greatly appreciated.

Slackware is a little different to Ubuntu (or Debian) in that regard in that repositories are handled differently. There's not normally any automatic updating unless I choose to do it myself. Some updates I would have to compile myself if I thought they were necessary.
I'll use ldd and see what comes up. Might reveal something. Thanks.

Ok, all the dependencies come up as met for the client, command and manager binaries.

I just discovered that if I switch to Simple View and then back it seems to work fine. I'm guessing this is something to do with the Skinning feature somehow.

It happens every time I connect to a client, be it the local machine or another one on my network. I also just discovered that it will not upload tasks, either. It's particular to this machine though as the same version uploads fine on my other Linux boxes, which are all Ubuntu 10.04, though the manager won't run on them. ldd boincmgr on those machines rattles off a bunch of unmet dependencies on gt2k.

I noticed in another thread comments about using dynamic/static linking and how the devs have chosen to go dynamic. As far as I can see the only "problems" they are addressing this way are related to cosmetics, size on the file server and bandwidth consumption. Up to v6.10.58 could be assumed to "just work" so long as you had a reasonably sane system. Now ... not so much. Never had this happen before so rather disappointed.
I downgraded to 6.12.33 and the upload at least works though the menu bar is still just as flakey.

In all fairness I should mention it's good to see the benchmark on this system come up with this version. The discrepancy between the Linux and Windows benchmarks have been the cause of some consternation for a while now.

Forgot to mention, minimizing the window and then maximizing/restoring it doesn't make any difference.

Little update:

I've discovered that Audacity exhibits the same symptoms and that a few people have had it happen to them. Not many, but a few at least. This suggests that there's some difficulty/incompatibility with the gtk+ or wxwidgets version on my system.
It might help if I knew which versions 6.12.33 and onwards are compiled against. Perhaps someone could enlighten me?

I also discovered that the client doesn't like my versions of libcurl, libcrypto and libssl (using the ldd boinc command), but it seems to run happily enough just the same so I won't chase those for the moment.

Ok, after hunting through versions for some time, it turns out that my wxwidgets version was/is too NEW.
I grabbed v6.12.43 and thankfully it lists which version it's compiled against: 2.8.11
My system was running wxWidgets 2.8.12
So far it's running nicely, though I will try to provoke it a little more before declaring this "solved".

Ok, it looks good.
The only niggle I've got is from the output of ldd boinc

./boinc: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by ./boinc)
./boinc: /usr/lib64/libcurl.so.4: no version information available (required by ./boinc)
./boinc: /usr/lib64/libssl.so.1.0.0: no version information available (required by ./boinc)

The required libs are there and the client runs, it's just sulking about the version information, so I'm not sure if it's a similar thing where my libs are newer than anticipated or something else. Since it works I'm not really worried about it.

As a suggestion, perhaps a page somewhere listing the lib versions these new dynamically linked BOINC versions are compiled against might be handy.

I all,

I recently installed Fedora 16, but I'm very new to Fedora since I was using Ubuntu before.

I dowloaded and installed the boinc_7.0.12_x86_64-pc-linux-gnu.sh.

this is the output of ldd boinc :

    ldd boinc
    ./boinc: /usr/lib64/libcurl.so.4: no version information available (required by ./boinc)
       linux-vdso.so.1 =>  (0x00007fffbd3c0000)
       libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00000036e1e00000)
       libssl.so.1.0.0 => not found
       libcrypto.so.1.0.0 => not found
       libdl.so.2 => /lib64/libdl.so.2 (0x00000031fba00000)
       libz.so.1 => /lib64/libz.so.1 (0x00000031fd200000)
       libXss.so.1 => /usr/lib64/libXss.so.1 (0x00007fa1f6055000)
       libpthread.so.0 => /lib64/libpthread.so.0 (0x00000031fb600000)
       libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003207600000)
       libm.so.6 => /lib64/libm.so.6 (0x00000031fc200000)
       libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000031fc600000)
       libc.so.6 => /lib64/libc.so.6 (0x00000031fb200000)
       libX11.so.6 => /usr/lib64/libX11.so.6 (0x00000031ff200000)
       libidn.so.11 => /lib64/libidn.so.11 (0x0000003213200000)
       liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x000000320fe00000)
       libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x0000003210e00000)
       librt.so.1 => /lib64/librt.so.1 (0x00000031fbe00000)
       libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x000000320c200000)
       libkrb5.so.3 => /lib64/libkrb5.so.3 (0x000000320c600000)
       libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x000000320ca00000)
       libcom_err.so.2 => /lib64/libcom_err.so.2 (0x000000320a200000)
       libssl3.so => /usr/lib64/libssl3.so (0x0000003209a00000)
       libsmime3.so => /usr/lib64/libsmime3.so (0x0000003209e00000)
       libnss3.so => /usr/lib64/libnss3.so (0x0000003209600000)
       libnssutil3.so => /usr/lib64/libnssutil3.so (0x0000003209200000)
       libplds4.so => /lib64/libplds4.so (0x0000003208a00000)
       libplc4.so => /lib64/libplc4.so (0x0000003208e00000)
       libnspr4.so => /lib64/libnspr4.so (0x0000003208600000)
       libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x0000003213a00000)
       /lib64/ld-linux-x86-64.so.2 (0x00000031fae00000)
       libXext.so.6 => /usr/lib64/libXext.so.6 (0x00000031ffe00000)
       libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00000031ffa00000)
       libresolv.so.2 => /lib64/libresolv.so.2 (0x00000031fd600000)
       libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x000000320ee00000)
       libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x000000320ba00000)
       libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x000000320ae00000)
       libssl.so.10 => /usr/lib64/libssl.so.10 (0x000000320e600000)
       libcrypto.so.10 => /lib64/libcrypto.so.10 (0x000000320a600000)
       libXau.so.6 => /usr/lib64/libXau.so.6 (0x00000031ff600000)
       libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003206e00000)
       libselinux.so.1 => /lib64/libselinux.so.1 (0x00000031fca00000)
       libfreebl3.so => /lib64/libfreebl3.so (0x0000003207200000)
    bash-4.2$ 

I don't know how to get it runing ...

---

You definitely need to install two libraries:

libssl.so.1.0.0 => not found
libcrypto.so.1.0.0 => not found

this bit means BOINC needs them but they're not on your system.
Have a hunt through your package manager for them and install them.

Hi Dark Angel,

Thanks for your answer, but I've always checked my package manager.

Opensssl-1.0.0g is installed, and I have libssl and libcrypto in the folder /usr/lib64/

A friend told me that this is a known bug of Boinc > 6.12.x with Fedora


I don't understand why 6.12.35 installed from package manager works, 7.0.12 (and backwards) installed from script doesn't work.

This issue seems only affecting Fedora...

---

I don't understand why 6.12.35 installed from package manager works, 7.0.12 (and backwards) installed from script doesn't work.

This issue seems only affecting Fedora...

BOINC from Berkeley is built on Ubuntu and therefore mainly compatible with that. To make it install on your system, you need all the correct library files installed and in the right place so this BOINC can get to them.

When you install BOINC from your package manager, it's built against the OS you run, with dynamic libraries. This means that it will run out of the box, without you needing to do too much work.

With 6.12 up to .33 there was a problem with Fedora 14 & 15, where the WxWidgets were incompatible. I don't know if that's been fixed yet and I can't ask our resident Linux guru as he went on a destruction spree the past weekend and got himself banished from these forums.

7.0.12 is still a development version of BOINC, it's nowhere near recommended yet. This is why most package manager maintainers will not have it available.

---

Hi Ageless,

Thanks a lot for that explanation, now I understand things better.

So I will use 6.12.35 from Fedora package manager instead of testing alpha versions :(

---

Hi Ageless,

Well, one of my teammates told me how to compile BOINC for Fedora 16, so now I'm runing Boinc 7.0.25 on Fedora_16_x64.

I talked about this with Daniel Lombraña González from the Test4Theory project, and I'll try to write a little "How-To" for Fedora users, as it's very easy to compile Boinc for Linux.

I can also send the script via email or download link if other Fedora Boinc users under want it.

Greetings,

---

You can send it to me, then I'll add it to the BOINC User Manual. With thanks. I PM'ed you my email address.

---

Ok, after hunting through versions for some time, it turns out that my wxwidgets version was/is too NEW.
I grabbed v6.12.43 and thankfully it lists which version it's compiled against: 2.8.11
My system was running wxWidgets 2.8.12
So far it's running nicely, though I will try to provoke it a little more before declaring this "solved".

This is a problem on gentoo and other distros - gonna try recompiling against 2.8.11 and will report back

Edit: Success on 1 Box will confirm on my other boxes
Edit 2: Confirmed this on 5 boxes

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Hi,

I'm having this problem in Debian as well, with BOINC 7.0.25. My system has the wx libraries version 2.8.12, and as Dark Angel pointed out, this somehow seems to be causing the problem.

Actually, it's more of an annoyance then a problem because switching back and forth between simple and advanced view modes gets the menus to display properly.

Still, is there any chance we'll see this fixed in a future release any time soon?