Crossed in the post. The difference between the repo versions and the BOINC version is that the repo ones are designed to run as a service, and BOINC's sh script is designed to run in user mode. The permissions are different, and - more importantly - the file locations are different.

Since you have a repo distribution already, I wouldn't mix'n'match - use Gianfranco's PPA for consistency.

I used that script to get around a different problem and didn't lose any tasks so presumably running the script as root installs in the usual /var/lib/boinc unlike the older self install scripts which put everything in boinc subdirectory of where you run the script from.

I haven't heard of Neon before, so I went looking for info, and found this: Neon: A Wannabe Linux Distro For KDE Lovers.
The 2nd paragraph says:

Neon looks and feels much like a Linux distribution, but its developers assert quite openly on their website that Neon is not a real Linux distro. It just installs and functions like one -- sort of.

So it may be a case of "Roll your own BOINC" for this OS.

I don't know who wrote that article. KDE Neon is a YABU. I've never had a package from the Ubuntu repository refuse to install. I've used this distro since it first came out. The person heading it up used to be in charge of Kubuntu for Canonical. The powers that be at Canonical honked them off (must be Tuesday, Wednesday, or Thursday) and they spun off for this KDE Neon thing.

It was "supposed" to have its own complete repositories. That hasn't happened. You also aren't saddled with a bunch of worthless KDE packages like KMail and Calligra like other distros shipping KDE desktops.

There is currently a brew-ha-ha going on with Qt Company vs the known universe. KDE community currently refusing to dump Qt but much of the known universe is looking at CopperSpice https://www.copperspice.com/ as a migration path of least pain. It's a fork of Qt 4.8 that removed all of the icky-nasty QML and JavaScript stuff. It probably needs another year to get the source base to where they want it. After that I suspect there will be another desktop which may or may not be like KDE that is based on CopperSpice and it will be available to other distros. It may or may not use a KDE Neon approach of basing off another distro's LTS.

It's true that Neon isn't a full blown distro. It's just a desktop environment patched on after the fact to Ubuntu. The same could be said for LXE, Gnome, or many other desktops if they chose to allow non-developer access to their more/most recent code instead of waiting for some "maintainer" for Ubuntu to get around to pulling the code. You see just how far behind the BOINC version is.

No. I'm willing to bet the PPA in question has something configured that works for Mint but not some/all other 18.04 YABUs. They all seem to be veering off towards different package management tools.

I'll try the shell script now. If it fails I can always force re-install.

---

Crossed in the post. The difference between the repo versions and the BOINC version is that the repo ones are designed to run as a service, and BOINC's sh script is designed to run in user mode. The permissions are different, and - more importantly - the file locations are different.

Since you have a repo distribution already, I wouldn't mix'n'match - use Gianfranco's PPA for consistency.

I used that script to get around a different problem and didn't lose any tasks so presumably running the script as root installs in the usual /var/lib/boinc unlike the older self install scripts which put everything in boinc subdirectory of where you run the script from.

It appears you had better luck than I.

http://www.logikalsolutions.com/wordpress/wp-content/uploads/2020/07/a-8.png

---

---