here is 5.4.052 with its changelog section :

2020-10-15 - Stefan Bader <stefan.bader@canonical.com>
linux (5.4.0-52.57) focal; urgency=medium
* focal/linux: 5.4.0-52.57 -proposed tracker (LP: #1899920)
* CVE-2020-12351 // CVE-2020-12352 // CVE-2020-24490
- Bluetooth: Disable High Speed by default
- Bluetooth: MGMT: Fix not checking if BT_HS is enabled
- [Config] Disable BlueZ highspeed support
* CVE-2020-12351
- Bluetooth: L2CAP: Fix calling sk_filter on non-socket based channel
* CVE-2020-12352
- Bluetooth: A2MP: Fix not initializing all members

2020-10-05 - Kleber Sacilotto de Souza <kleber.souza@canonical.com>
linux (5.4.0-51.56) focal; urgency=medium
* Packaging resync (LP: #1786013)
- update dkms package versions

2020-09-30 - Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
linux (5.4.0-50.55) focal; urgency=medium
* CVE-2020-16119
- SAUCE: dccp: avoid double free of ccid on child socket
* CVE-2020-16120
- Revert "UBUNTU: SAUCE: overlayfs: ensure mounter privileges when reading
directories"
- ovl: pass correct flags for opening real directory
- ovl: switch to mounter creds in readdir
- ovl: verify permissions in ovl_path_open()
- ovl: call secutiry hook in ovl_real_ioctl()
- ovl: check permission to open real file

Here is 5.4.058 with its changelog section :

2020-12-09 - Khalid Elmously <khalid.elmously@canonical.com>
linux (5.4.0-58.64) focal; urgency=medium
* focal/linux: 5.4.0-58.64 -proposed tracker (LP: #1907390)
* Packaging resync (LP: #1786013)
- update dkms package versions
* raid10: discard leads to corrupted file system (LP: #1907262)
- Revert "dm raid: remove unnecessary discard limits for raid10"
- Revert "dm raid: fix discard limits for raid1 and raid10"
- Revert "md/raid10: improve discard request for far layout"
- Revert "md/raid10: improve raid10 discard request"
- Revert "md/raid10: pull codes that wait for blocked dev into one function"
- Revert "md/raid10: extend r10bio devs to raid disks"
- Revert "md: add md_submit_discard_bio() for submitting discard bio"

2020-11-23 - Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
linux (5.4.0-56.62) focal; urgency=medium
* focal/linux: 5.4.0-56.62 -proposed tracker (LP: #1905300)
* CVE-2020-4788
- selftests/powerpc: rfi_flush: disable entry flush if present
- powerpc/64s: flush L1D on kernel entry
- powerpc/64s: flush L1D after user accesses
- selftests/powerpc: entry flush test

I am going to update the linux kernel on this machine and see what happens.

Not surprisingly, after updating to the 5.4.0-58 Linux kernel, all the remaining twelve work units ended in "Validate error" after running only a few seconds.
https://quchempedia.univ-angers.fr/athome/results.php?hostid=3052&offset=0&show_names=0&state=5&appid=

So there is the smoking gun. It is something that changed between 5.4.0-52 and 5.4.0.-58.
(Or else between BOINC 7.16.11 and 7.16.14).
Maybe that will help.

It helps a lot !
At least we have something.
I have no idea how to solve this at the moment.

I am also seeing a lot of errors, although will point out that I'm running Linux Mint VMs and they have had not had recent kernel or boinc upgrades. They have run a lot of QuChem in the past with no issues.

I think the problem is solved, but I can't check it since my machine is not allowed now.
It was not the Linux kernel version, but BOINC 7.16.14, which I obtained from PPA costamagnagianfranco.

I fixed it with the expert advice from Gunde on the LHC forum, where I could not run CMS (a VirtualBox project).
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5560
Basically, if you have that PPA version, you go to "software and update" and uncheck line for that PPA then:
sudo apt remove boinc-client boinc-manager
sudo apt install boinc-client boinc-manager

That will install BOINC from the apt repository.
In the case of Ubuntu 20.04.1, it will be BOINC 7.16.6.
In the case of Ubuntu 18.04.5, it will be BOINC 7.9.3.
Either should work with QuChemPedIA, I expect.

I think the problem is solved, but I can't check it since my machine is not allowed now.
It was not the Linux kernel version, but BOINC 7.16.14, which I obtained from PPA costamagnagianfranco.

I fixed it with the expert advice from Gunde on the LHC forum, where I could not run CMS (a VirtualBox project).
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5560
Basically, if you have that PPA version, you go to "software and update" and uncheck line for that PPA then:
sudo apt remove boinc-client boinc-manager
sudo apt install boinc-client boinc-manager

That will install BOINC from the apt repository.
In the case of Ubuntu 20.04.1, it will be BOINC 7.16.6.
In the case of Ubuntu 18.04.5, it will be BOINC 7.9.3.
Either should work with QuChemPedIA, I expect.

I can whitelist your host if you want to test ? Just give me the host id.

I can whitelist your host if you want to test ? Just give me the host id.

I would like to try it on ID: 5132
That is a Ryzen 3600 that I had upgraded to Ubuntu 20.04.1 and was causing problems with BOINC 7.16.14.
It is now working on VirtualBox projects, and even though I am not using VB for QuChemPedIA, I think the problems are related.

5132 whitelisted ! Be careful not to make too many errors.

They are now running fine and completing OK.
Just don't use BOINC 7.16.4.
https://quchempedia.univ-angers.fr/athome/results.php?hostid=5132

Thanks for the feedback , Jim1348.
It is christmas , before the date.



I have found a post of Jord in the boinc forum ,he speaks about a change in the way , the user has to download Boinc.It was the 29 November.

People that want to crunch on Linux have to go their software repository instead of downloading the latest version here.

That's because that's the new policy. The package maintainers add the newer/newest versions, the BOINC release manager(s) no longer do. Besides, I don't even think we have a release manager for BOINC on Linux.

It's done this way that the package that's built has all the correct libraries for that built for that Linux distribution, instead of BOINC building a version that's broken on 3/4s of the distros out here.

So, for linux and probably mac users , it is advised to download Boinc through their distro repository.
It is more secure.
Don't use neither the boinc installer of the boinc site , nor the personal package archive (ppa) costamagnagianfranco-ppa.
Thus , you will avoid incompatibility between the boinc code and the libraries needed.
The drawback is that you will crunch with a lower or equal version than the latest displayed on the boinc site .
But more important is that the behavior of boinc is correct to not discourage users.

Happy Christmas , everyone !!!

I know nothing about Linux but it sure is nice to see a resolution to this sort of issue.

Got kernel 5.10.1 on my SuSE Linux Virtual Machine enlisted in Science United. All tasks seem to run well.
Tullio

---

I think the problem is solved, but I can't check it since my machine is not allowed now.
It was not the Linux kernel version, but BOINC 7.16.14, which I obtained from PPA costamagnagianfranco.

I fixed it with the expert advice from Gunde on the LHC forum, where I could not run CMS (a VirtualBox project).
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5560
Basically, if you have that PPA version, you go to "software and update" and uncheck line for that PPA then:
sudo apt remove boinc-client boinc-manager
sudo apt install boinc-client boinc-manager

That will install BOINC from the apt repository.
In the case of Ubuntu 20.04.1, it will be BOINC 7.16.6.
In the case of Ubuntu 18.04.5, it will be BOINC 7.9.3.
Either should work with QuChemPedIA, I expect.

This solution seems to work !
If you have a blacklisted host and want to test the patch, ask me for whitelist.