Latest BOINC version for Windows downloaded yesterday. Running six tasks under WINE with XUbuntu23.04 as the host. 6 CPDN tasks running. The manager is currently stuck on the tasks tab and not responding to keyboard or mouse. I have another instance of BOINC running in a VM with just one task and that is behaving normally though it is one or two versions back. Half an hour ago, it was responding normally. The tasks are all running with no problems so I will probably wait just over a week for them all to complete before doing anything assuming they all run to completion. Mouse and KB working normally for all other programs.

Ryzen7 8 real cores, 32GB RAM

Wanted to look at event log without messing about with files. Used boinccmd to suspend tasks then shut down the client. xkill to stop the manager. All restarted fine. Once there are fewer tasks to risk losing, i will try and reproduce.

Happened again after clicking on help>about.

When work finishes will see if it consistently does it.

When work finishes will see if it consistently does it.

Note to self: Set all projects to "no new tasks."

Now have a testing branch task that will take about a month to finish. Currently responding to mouse and KB but event log refuses to open. Able to find the file and look at it with kate once I remembered to look in .wine/drive_c/ProgramData/BOINC rather than /var/lib/boinc-client. Strangely my other copy of the latest Windows version does not have these problems in the VM.

After a reboot which fortunately did not result in any tasks being lost, After a while of switching between tasks etc. Tools>event log does not open the log and I have to go to stdoutdae.text which autoupdates in kate.

Just wondering if anyone else has experienced this with the latest Windows client either in WINE or running natively? I don't have a real Windows machine to test this with.

Another oddity.

08-Jul-2023 18:14:28 [---] Number of usable CPUs has changed from 8 to 9.
08-Jul-2023 18:20:09 [---] Number of usable CPUs has changed from 9 to 8.

It is a couple of days since I last changed computing preferences. I haven't spotted this particular behaviour on previous versions but I wasn't looking for it either so I don't know if this is something new or not?

Could be new with v7.22

I've seen that when different values are set for 'use at most ... % of the CPUs' in the "in use" and "not in use" sections.