I am running Testing with the liquorix kernel.

Right now I have Boinc 6.10.52 on here. I have tried 6.10.58, 6.12.8 and 6.12.18 (all for 64bit linux).

I have, for months, been running the 6.12.8 version.

Boinc is installed in my home folder as it has been for nearly 2 years.

Rebooted after trying to test an Ubuntu LiveCD for the 11.04B1 (Failed big time). I turned off this drive in bios for that test. This has been done many times over the years of testing as I use a different drive for that and want no contamination of my main drive. I did have some problems booting that were corrected by reinstalling my fglrx-driver package.

The only problem is that Boinc will not run at all. None of those versions. They all behave the same way.

Open boincmngr from menu and it comes up blank and "disconnected".

Go to Advanced/Select computer. Has the option for "Debian". This is correct. Select that and enter the password for Boinc or the password for Debian and it tries to connect but does not.

Any clues for the clueless?

Move the BOINC folder out of the way (i.e. rename) and try again? Are the permissions right?

Yup everything was right and I did install several versions to try them and none of them would work.

Beats me. Been using it in the home folder for several Ubuntu test cycles were I was running several installs of the testing OS.

I would keep them all up to date but had 2 that got updated last after checking to see if anything broke in the others. Ran the pre-release OS' as production OS'. I wanted boinc to be portable and it was handy on a few occasions. One of my primary OS' would pack it in and I would just go to the other and copy the file over to it, fire it up and it would never now the difference (same drive on the same machine and the same user name).

This time it just would not work. Decided to just give up on that and installed from the Debian repo this afternoon. Running great but it is not portable which is fine as this is the only OS I spend any time with. Ubuntu has become too silly for serious work for me.

So I will never know what the problem was but I have things running and will be marking this thread as solved. Not a real good solution but it did work.

I will fight it out some other time if it happens again.

Thanks for the reply.