Hi. I have a trouble with the Boinc Manager. After an Ubuntu distro reinstallation (ver. 16.04 lts), the UI is blocked on the state "reception of the state in progress". I tried to refresh and reset project already, but without results. Can you help me? Thanks

---

1. Make sure that the BOINC client binary is running before trying to run BOINC Manager. Under Linux starting BOINC Manager does not auto-start the client.
2. Make sure you added the BOINC binary and BOINC Manager binary through the firewall, that they are allowed to 'talk' to each other on TCP port 31416. The BOINC binary needs separate internet access on TCP ports 80 and 443.
3. Did you reinstall BOINC after you reinstalled the OS? Else it could be a simple permission problem.

Resetting the project will not fix any problems you have with BOINC Manager, as this is purely a graphical user interface that allows you to control the BOINC client, it has no interactions with the Seti project.

---

In common with many replies to Linux questions, this one assumes that the asker knows how to do the actions suggested. "Make sure the BOINC client is running" ... but how? The installation instructions provided with the Seti@home package do not match what is required under Ubuntu 16.04 LTS and do not work.

Many new Linux users want to carry on running the Seti@home project, but don't know how to get it working. It was straightforward under Windows, but Linux (Ubuntu in my case) is a different matter. Experienced users do not appear to want to help beginners.

I cannot even find the firewall, let alone check what is allowed through it. The BOINC Manager does not open to anything useful. I am beginning to wonder if it worth bothering with at all.

ps -lf | grep boinc

root@raspberrypi /var/lib/boinc-client # ps -lf | grep boinc
0 S root 14520 14228 0 80 0 - 891 pipe_w 20:06 pts/0 00:00:00 grep --color=auto boinc

We want to help

---

I am beginning to wonder if it worth bothering with at all.

Purely as critical commentary, but I find a lot of things under Linux are far more difficult than they need to be and generally isn't worth the time trying to figure it out when things simply work under Windows. I say this as someone who still owns copies of Caldera OpenLinux 2.3 and Red Hat Linux 5.2 from circa 1997/1998. Admittedly things have gotten a lot better, but too many things require fiddling with WINE, finding an alternative program that runs under Linux natively (and thus dealing with the learning curve), or simply requiring going back into Windows for things like gaming. My logic quickly became: if I still need to keep a Windows license around, why not just stay in Windows?

I sympathize with anyone looking to learn stuff in Linux. The OS always seems so fascinating to me, but I feel I can do more in Windows. I keep checking out new Linux distros but I still haven't found anything worthwhile to make me stay.

The fun (and frustration) is getting it to work ;)

---

I've moved on from the fun of making an OS work some 20 years ago, and now enjoy scripting in Powershell and customizing and deploying Windows client and server to thousands of machines.