Not familiar with linux (but it is on my wish list) so I am not sure how to implement this on the subject system:

Set NO NEW TASKS. And allow the system to run out of work.
Once there are no WU’s to do or in process and the waiting to be sent queue is empty then uninstall the undesired S/W, reboot and install the desired version.
Let us know how it works out.

BobbyB,

Before uninstalling BOINC, after stopping the BOINC service, it is always good to make a (backup) copy of the BOINC (data) directory.
Take these easy three steps:
* Stop the BOINC service
* Make a backup copy of the BOINC (data) directory
* Uninstall BOINC

Example of making a copy (assuming ~boinc is your BOINC data directory):

sudo cp -a ~boinc ~root/boinc.save.$$

Adri

OK, so I've started the process of draining the queues. I have about 2 days of work left per CPU.

Tried the archive command which Adri gave listed and found where it stashed the backup.

I tested removing the Boinc using Synaptics and it asks whether to also remove the data directory. So this is a good sign.

BobbyB,
I've just been setting up a mini-PC with a Ryzen 7840HS, using XUbuntu 24.04 (mandatory 7.24.1 client!), which means I've now got two Ryzens and an i7-7700 on the new client...

The other systems on 7.24.1 have never shown your symptom, but as soon as this new box returned results I saw the same symptoms! As it's not a "daily driver" system, I disabled the "Suspend when non-BOINC CPU usage" option in both the "computer in use" and "computer not in use" sections, and that seems to have stopped it!

(Note that I have not disabled the "In use" tests on either of them, as I do occasionally use them for non-BOINC purposes :-)

Now, what differences are there between my systems?

• Both the older systems have a slightly older build of the client (as far as I can determine)
  
• The older systems are still running XUbuntu 22.04 versions
  
• The Intel system is on kernel 5.15 and the older Ryzen is on kernel 6.5, whereas the new Ryzen is on kernel 6.8
  

It isn't memory-size related (the Ryzens have 32GB and the Intel only has 16GB!) so my instinct is that it's an issue with "busy detection" that is either kernel-specific or introduced in a recent build -- I've not made any great effort to see if there's a bug logged, I'm afraid...

By the way, I have another Ryzen mini-PC (a 5600H), but that's on client 7.20.5 and kernel 5.15; no problems there either!

Good luck with client 7.18 for as long as it is available for whatever Linux flavour (and kernes) you might have :-) -- with my use of app_config.xml files for both WCG and non-WCG projects, I couldn't get off it fast enough!

Cheers - Al.