I have now installed boinc 4.43 on two linux boxes. Both are PIIIs. One is running gentoo linux, and the other has ubuntu, both the latest builds, and both have 2.6 series kernels. The gentoo box has KDE 3.4 installed, the ubuntu box has Gnome. In both cases when I run the boinc manager gui client it starts by popping up a box that says \"Connection failed\", and when I open one of the pull down menus my X session has been known to stop working. I can use shortcut keys to go to a console prompt, and kill X, but that\'s about all. On other occasions I have been able to quit. When I try running from a terminal session I get 2 Connection refused\" messages. Then it says \"Failed with error 2\", there are two calls to get_socket_error() that appear to return 111, and then it says that it has tried both ports and it\'s giving up.

Neither linux box is running a firewall as far as I am aware. My broadband router has a firewall (which I don\'t really know how to modify the configuration of - cringe with shame), but both the command line client, and the Windows boinc manager seem to be able to cope with the same situation.

In general I\'m quite happy running the command line client, but I\'d like to know what might be going on with the manager. Does it only work with Red Hat, or something?

I am not 100% up on this latest vesion of boinc, but I usually start boinc (cd BOINC ./boinc) in a terminal window first then run the manager. Is this what you are trying? I don't think the manager will start up everything on it's own.

The instructions that I have been able to find so far for using this latest version are pretty sparse. I run FC4 with Gnome, but as far as I know other users have it running on various flavours of Linux.

Dave

+1 for DaveN

Boinc and BOIncmanager are 2 different softwares: You have to start boinc (cd ~/BOINC and ./boinc) and then start the boincmanager: the manager tries to connect to boinc on the localhost.

You can also read <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=2672#13147">this</a> thread for more info for newbies (sorry, I don't know if you're a newbie :o))

&gt; +1 for DaveN
&gt;
&gt; Boinc and BOIncmanager are 2 different softwares: You have to start boinc (cd
&gt; ~/BOINC and ./boinc) and then start the boincmanager: the manager tries to
&gt; connect to boinc on the localhost.
&gt;
&gt; You can also read <a> href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=2672#13147"&gt;this</a>
&gt; thread for more info for newbies (sorry, I don't know if you're a newbie :o))
&gt;
Well, newbie is a relative term I suppose. No offence taken. I guess I just assumed that the linux boincmgr was the equivalent of the Windows program that looks exactly the same. It's nice to see that I'm not Robinson Crusoe in this belief. My message to the authors of the software would be (1) their "Connection refused" dialog could be improved to say something like "Dolt! Start the command line client before running the GUI!" (2) maybe they could improve the run_client script to prompt to run the boincmgr program after starting the client. If I knew squat about linux scripting I could probably run something up along those lines (memo to self: this could be a beginner's python project...)