collatz: Notice from BOINC
Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
6/3/2020 12:06:07 PM

The above message is STILL appearing whenever I start BOINC. This annoys me to no end. You said it was going to be deactivated in the NEXT update. YOU LIE!!!!!!!

OK, we should have said "it will be fixed in the next planned update". That's still the plan: https://github.com/BOINC/boinc/pull/3749

But in the meantime, the incompetent BOINC administrators got caught out by an expired security certificate, and made an unplanned update which didn't include the planned updates. So the 'next' update became the 'next but [one?] [two?] [who knows?] update'.

I asked about those fixes being included and was ignored. So yes. Fun.

---

The latest BOINC version, as known to BOINC at the time of writing, is v7.16.7

So why is my Linux machine being offered v7.16.15 by Gianfranco's PPA?

Nightly tarball?

Nightly tarball?

No, a fully fledged system update.

I don't know. You should ask him why he jumped from 7.16.6 to 7.16.15: https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc/+builds?build_state=built

I could, I suppose, but I think I'd just be getting even further out of my depth. I'll sleep on it.

It's possible he ran some test versions, internally or with the other developers. But other than that I really can't think of anything.

Because in order to install Boinc from him, you must add his PPAs into the repositories.
In other words, you're loading the latest 'beta' versions, that could have some instability (like 'Your settings do not allow fetching tasks for CPU...'

If you installed Ubuntu 20.04 or a variant, without PPA, the latest version will be 7.16.6, until someone decides that it's time to provide the repositories with an updated version.

Still lied. You can't get around that.

Well, the programmers and developers don't frequent these forums so if you want to rub against the good volunteers that do frequent these forums and call us all liars because no one checked the validity of some certificate for crucial communications with a lot of projects then be my guest. Humans make mistakes.

We cannot predict what the BOINC Release Manager is going to add to a next BOINC unless one of us becomes that person next. The present RM does what he wants and listens to no-one.

So for future reference, some future BOINC will have the fixes added and most probably have new annoyances added. Which then take absolutely forever to get fixed again.

I don't even know why this version needed a new version number, seeing how they're in the process of releasing an Android client with the new certificates file with the same version number as the present stable version. That could've been done for the Windows version as well. (and still nothing about the 32bit client, right?)

---

Nightly tarball?

No, a fully fledged system update.

https://i.imgur.com/9F0bTnZ.png

Well, I took my courage in both hands, donned PPE, and installed it.

2020-06-04 09:33:07 upgrade boinc-client-nvidia-cuda:amd64 7.16.6+dfsg+202005240954~ubuntu18.04.1 7.16.15+dfsg+202006021756~ubuntu18.04.1
2020-06-04 09:33:32 status installed boinc-client-nvidia-cuda:amd64 7.16.15+dfsg+202006021756~ubuntu18.04.1

-- Logs begin at Mon 2020-02-03 12:48:12 GMT, end at Thu 2020-06-04 09:54:09 BST. --
Jun 04 09:34:29 Rosa systemd[1]: Started Berkeley Open Infrastructure Network Computing Client.
Jun 04 09:34:29 Rosa boinc[628]: 04-Jun-2020 09:34:29 [---] Starting BOINC client version 7.17.0 for x86_64-pc-linux-gnu
Jun 04 09:34:29 Rosa boinc[628]: 04-Jun-2020 09:34:29 [---] log flags: file_xfer, sched_ops, task, cpu_sched, sched_op_debug, unparsed_xml
Jun 04 09:34:29 Rosa boinc[628]: 04-Jun-2020 09:34:29 [---] Libraries: libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Jun 04 09:34:29 Rosa boinc[628]: 04-Jun-2020 09:34:29 [---] Data directory: /var/lib/boinc-client
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [---] OpenCL: NVIDIA GPU 0: GeForce GTX 1660 SUPER (driver version 440.82, device version OpenCL 1.2 CUDA, 5943MB, 5943MB available, 5153 GFLOPS peak)
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [---] OpenCL: NVIDIA GPU 1: GeForce GTX 1660 SUPER (driver version 440.82, device version OpenCL 1.2 CUDA, 5945MB, 5945MB available, 5153 GFLOPS peak)
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [SETI@home] Found app_info.xml; using anonymous platform
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [---] App version needs CUDA but GPU doesn't support it
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [---] App version needs CUDA but GPU doesn't support it
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [---] App version needs CUDA but GPU doesn't support it
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [GPUGRID] Application uses missing NVIDIA GPU
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [GPUGRID] Missing coprocessor for task 1neeA01_379_4-TONI_MDADex2sn-8-50-RND2183_0
Jun 04 09:34:31 Rosa boinc[628]: 04-Jun-2020 09:34:31 [GPUGRID] Missing coprocessor for task 1svuA02_413_4-TONI_MDADex2ss-8-50-RND6622_0

So it's v7.17.0 (master), but without the pre-release tag.

When I install a package called "boinc-client-nvidia-cuda", I expect it to wait for the CUDA driver to load before launching...

Off to find a bug reporting site.

Still lied. You can't get around that.

You’ve obviously never worked in a computer development environment and you know not of what you speak.

There are two distinct types of implementation, what you might call an update. There are scheduled implementations and emergency fixes. You NEVER rush in a scheduled implementation to make an emergency fix, that is a sure fire recipe for disaster and bugs in the future. If you have a problem that blocks the users you develop and test a fix for that problem against the live system and implement it in isolation. You then go back and regression test your scheduled implementation against the updated live system and, hopefully, make the updates to the original schedule.

Given that no-one can predict when an emergency fix will be necessary the information that you were given was true to the best knowledge that the responders could possibly have had, it was therefore no lie.

For you to come in here insulting the people who are doing their very best to help and who are doing so in their own time without reward is totally out of order. I suggest that you apologise to them for your ignorance and rudeness and then crawl back where you came from.

Always fun to see how people still can't use versions.php
But then I shouldn't laugh as I've been there as well. :)