I'm also getting disk space errors even though I have 11GB free. The error I get is I've tried starting up the GUI manager but it wants a password - I've tried all I can think of, and also wants to be associated with a project - again I've cut and pasted all sorts of things in here, but none seem to work. Is there a boincmgr user guide somewhere or has someone any advice?
Greg

(Kubuntu boinc in command line mode)

boinc is in the root partition, with 11GB to spare. I tried connecting to local host with the password the gui fills in, without a password and with the very long password in gui_rpc_auth.cfg but it will accept none of these options. Is there any other way of getting rid of this error message? Greg

I think I might have overcome the problem in a 'try everything' sort of a way, like this:
1. Close the boinc terminal, which stops the boinc client running
2. run the manager. In my case, under KUBUNTU this means typing in a terminal, when in the BOINC folder
The manager asks for the URL of the project, which is www.worldcommunitygrid.org. It then seems to grumble with errors but asked for my grid name and password, for which I used the original registration details with world community grid, and appeared to be linked to my project.
3. Then I reset the project - no idea what this does but it did ask me if I was really sure that I wanted to do this.
4. close the manager and restart boinc in the usual linux command line way.

It is running OK at the moment - time will tell though.

Conclusion - I needed to reset the project but have really fought to do this. Surely It can be made easier for users like me, who have some technical knowledge but are not experts. I've looked for a simpleton's user guide to the manager but haven't found one as yet.
Greg

Resetting the project deletes all the project specific files. In theory, it should produce the same effect as detaching then reattaching to a project, but in practice doing that may leave some old files lying around (I haven't tested this recently, so I could be wrong).

For most Linuxes, I strongly recommend you use the port system and have it all installed automatically. The install will sort out the permission issues, and create a user that BOINC runs as, minimising security issues. It also sets up BOINC to run as a service, so it automatically starts up with your computer.

You can then run BOINC Manager or boinc_cmd to manage it while it is running.

In the next BOINC release, it is hoped that the installation will be better designed, and that all users will be directed to the best installation script - the default script provided by Berkeley is very basic and really not sufficient.

This message showed up at BOINC Dev, that could explain the error-ing of for instance faah.