I don't seem to be completing the installation. I followed the instructions:
sudo apt update
sudo apt install gnupg2 curl
sudo mkdir -p /etc/apt/keyrings
sudo curl -fsSL https://boinc.berkeley.edu/dl/linux/stable/jammy/boinc.gpg | sudo gpg --dearmor -o /etc/apt/keyrings/boinc.gpg
sudo echo deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/boinc.gpg] https://boinc.berkeley.edu/dl/linux/stable/jammy jammy main | sudo tee /etc/apt/sources.list.d/boinc.list > /dev/null
sudo apt update
sudo apt install boinc-client boinc-manager

aurum@Rig-05:~$ sudo apt install boinc-client boinc-manager -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
boinc-client boinc-manager
0 upgraded, 2 newly installed, 0 to remove and 8 not upgraded.
Need to get 15.7 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://boinc.berkeley.edu/dl/linux/stable/jammy jammy/main amd64 boinc-client amd64 8.2.8-3429 [2,976 kB]
Get:2 https://boinc.berkeley.edu/dl/linux/stable/jammy jammy/main amd64 boinc-manager amd64 8.2.8-3429 [12.7 MB]
Fetched 15.7 MB in 1s (15.6 MB/s)
Selecting previously unselected package boinc-client.
(Reading database ... 576901 files and directories currently installed.)
Preparing to unpack .../boinc-client_8.2.8-3429_amd64.deb ...
Unpacking boinc-client (8.2.8-3429) ...
Selecting previously unselected package boinc-manager.
Preparing to unpack .../boinc-manager_8.2.8-3429_amd64.deb ...
Unpacking boinc-manager (8.2.8-3429) ...
Setting up boinc-client (8.2.8-3429) ...
usermod: no changes
Synchronizing state of boinc-client.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable boinc-client
Job for boinc-client.service failed because the control process exited with error code.
See "systemctl status boinc-client.service" and "journalctl -xeu boinc-client.service" for details.
dpkg: error processing package boinc-client (--configure):
installed boinc-client package post-installation script subprocess returned error exit status 1
Setting up boinc-manager (8.2.8-3429) ...
Errors were encountered while processing:
boinc-client
E: Sub-process /usr/bin/dpkg returned an error code (1)

aurum@Rig-05:~$ systemctl status boinc-client.service
× boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/etc/systemd/system/boinc-client.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2025-11-26 08:17:18 PST; 7min ago
Docs: man:boinc(1)
Process: 4929 ExecStartPre=/bin/sh -c /bin/chmod +x /sbin/create-boinc-cgroup && /sbin/create-boinc-cgroup (code=exited, status=1/FAILURE)
Process: 4974 ExecStopPost=/bin/rm -f lockfile (code=exited, status=0/SUCCESS)
CPU: 102ms

Nov 26 08:17:18 Rig-05 sh[4968]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4969]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4969]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4970]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4970]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4971]: chown: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4972]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Nov 26 08:17:18 Rig-05 systemd[1]: boinc-client.service: Control process exited, code=exited, status=1/FAILURE
Nov 26 08:17:18 Rig-05 systemd[1]: boinc-client.service: Failed with result 'exit-code'.
Nov 26 08:17:18 Rig-05 systemd[1]: Failed to start Berkeley Open Infrastructure Network Computing Client.

aurum@Rig-05:~$ journalctl -xeu boinc-client.service
░░
░░ The job identifier is 1627.
Nov 26 08:17:18 Rig-05 sh[4934]: chown: cannot access '/sys/fs/cgroup/freezer/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4935]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4937]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4938]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4940]: chown: cannot access '/sys/fs/cgroup/devices/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4941]: chmod: cannot access '/sys/fs/cgroup/devices/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4943]: chown: cannot access '/sys/fs/cgroup/memory/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4944]: chmod: cannot access '/sys/fs/cgroup/memory/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4946]: chown: cannot access '/sys/fs/cgroup/cpu,cpuacct/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4947]: chmod: cannot access '/sys/fs/cgroup/cpu,cpuacct/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4949]: chown: cannot access '/sys/fs/cgroup/pids/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4950]: chmod: cannot access '/sys/fs/cgroup/pids/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4952]: chown: cannot access '/sys/fs/cgroup/blkio/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4953]: chmod: cannot access '/sys/fs/cgroup/blkio/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4955]: chown: cannot access '/sys/fs/cgroup/hugetlb/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4956]: chmod: cannot access '/sys/fs/cgroup/hugetlb/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4958]: chown: cannot access '/sys/fs/cgroup/net_cls/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4959]: chmod: cannot access '/sys/fs/cgroup/net_cls/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4961]: chown: cannot access '/sys/fs/cgroup/net_prio/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4962]: chmod: cannot access '/sys/fs/cgroup/net_prio/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4964]: chown: cannot access '/sys/fs/cgroup/perf_event/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4965]: chmod: cannot access '/sys/fs/cgroup/perf_event/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4967]: chown: cannot access '/sys/fs/cgroup/freezer/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4968]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4969]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4969]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4970]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4970]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4971]: chown: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4972]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Nov 26 08:17:18 Rig-05 systemd[1]: boinc-client.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStartPre= process belonging to unit boinc-client.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 26 08:17:18 Rig-05 systemd[1]: boinc-client.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit boinc-client.service has entered the 'failed' state with result 'exit-code'.
Nov 26 08:17:18 Rig-05 systemd[1]: Failed to start Berkeley Open Infrastructure Network Computing Client.
░░ Subject: A start job for unit boinc-client.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit boinc-client.service has finished with a failure.
░░
░░ The job identifier is 1627 and the job result is failed.
lines 666-719/719 (END)

We do not mess with this in our package.
Did you install previously BOINC package from some other location package from the distro repo, PPA, etc)?

---

BOINC maintainer.
For any insight, check my BOINC Development Blog.

In reply to Vitalii Koshura's message of 26 Nov 2025:

We do not mess with this in our package.
Did you install previously BOINC package from some other location package from the distro repo, PPA, etc)?

No. This is a new build Linux Mint 21.3 computer. I installed using these instructions as shown in my first post. I do not understand your comment.
https://boinc.berkeley.edu/linux_install.php?action=submit&os_num=4&version_num=2&build=stable
It seems to install but behaves strangely. I inserted my password in gui_rpc_auth.cfg and rebooted. BOINC does not start on booting but requires clicking the desktop icon to launch. It is not visible in BOINC Task JS 2.6.2 but all my other computers are.

In our package we don't do anything like that:

Process: 4929 ExecStartPre=/bin/sh -c /bin/chmod +x /sbin/create-boinc-cgroup && /sbin/create-boinc-cgroup (code=exited, status=1/FAILURE)
Process: 4974 ExecStopPost=/bin/rm -f lockfile (code=exited, status=0/SUCCESS)

So I have no idea where does this come from.
So I suspect you have previously installed BOINC from some other location.

And I have no idea about BoincTasks since we don't support it.

---

BOINC maintainer.
For any insight, check my BOINC Development Blog.

I told you this is a new build computer so how could I have installed from somewhere else?
I followed your instructions exactly and they failed.

In reply to Aurum's message of 26 Nov 2025:

aurum@Rig-05:~$ systemctl status boinc-client.service
× boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/etc/systemd/system/boinc-client.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2025-11-26 08:17:18 PST; 7min ago
Docs: man:boinc(1)
Process: 4929 ExecStartPre=/bin/sh -c /bin/chmod +x /sbin/create-boinc-cgroup && /sbin/create-boinc-cgroup (code=exited, status=1/FAILURE)
Process: 4974 ExecStopPost=/bin/rm -f lockfile (code=exited, status=0/SUCCESS)
CPU: 102ms

Nov 26 08:17:18 Rig-05 sh[4968]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/tasks': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4969]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4969]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4970]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4970]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4971]: chown: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Nov 26 08:17:18 Rig-05 sh[4972]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Nov 26 08:17:18 Rig-05 systemd[1]: boinc-client.service: Control process exited, code=exited, status=1/FAILURE
Nov 26 08:17:18 Rig-05 systemd[1]: boinc-client.service: Failed with result 'exit-code'.
Nov 26 08:17:18 Rig-05 systemd[1]: Failed to start Berkeley Open Infrastructure Network Computing Client.

The following line from your logs show that you do not use the original boinc service file:

Process: 4929 ExecStartPre=/bin/sh -c /bin/chmod +x /sbin/create-boinc-cgroup && /sbin/create-boinc-cgroup (code=exited, status=1/FAILURE)

/sbin/create-boinc-cgroup was a script from LHC@home that prepared cgroups v1 based Linux systems to allow certain apps from the project to use suspend/resume.
The script has been deprecated long ago and must not be used any more.
On recent systems it fails to execute and since you call it from your service file the boinc service doesn't start as a whole.