Anyone know what this is or how to fix it?

There's a previous thread but I can't reply to it, I guess it's locked? https://boinc.berkeley.edu/forum_thread.php?id=14249

~> sudo systemctl status boinc-client
● boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2023-02-05 11:08:51 EST; 1h 0min ago
Docs: man:boinc(1)
Main PID: 1962 (boinc)
Tasks: 2 (limit: 19062)
Memory: 40.1M
CPU: 5.873s
CGroup: /system.slice/boinc-client.service
└─1962 /usr/bin/boinc

Feb 05 12:08:48 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:48 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:49 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:49 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:50 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:50 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:51 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:51 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:52 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 05 12:08:52 shuttle boinc[1962]: Authorization required, but no authorization protocol specified


~> tail -f /var/log/syslog | grep boinc
Feb 5 11:59:57 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 5 11:59:58 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 5 11:59:58 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 5 11:59:59 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 5 12:00:00 shuttle boinc[1962]: message repeated 3 times: [ Authorization required, but no authorization protocol specified]
Feb 5 12:00:01 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 5 12:00:02 shuttle boinc[1962]: message repeated 3 times: [ Authorization required, but no authorization protocol specified]
Feb 5 12:00:03 shuttle boinc[1962]: Authorization required, but no authorization protocol specified
Feb 5 12:00:04 shuttle boinc[1962]: message repeated 3 times: [ Authorization required, but no authorization protocol specified]
Feb 5 12:00:06 shuttle boinc[1962]: Authorization required, but no authorization protocol specified

~> boinc --version
7.18.1 x86_64-pc-linux-gnu

~> uname -a
Linux shuttle 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

~> cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

If I run

~> sudo systemctl disable boinc-client

and reboot it stops spamming syslog every second

You really should install the latest BOINC client. Unfortunately, the client you are using was never meant for release to amd64 hosts. It was meant only for Android users. But the distro maintainers screwed up and grabbed the wrong branch to package into the distro.

You should grab the client from here. https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc

The issue you are experiencing is a permission problem for the local user that the BOINC devs introduced earlier for security purposes.

Normally adding your local user into the boinc group solves the problem. I am sure this has been extensively discussed in the forums here. I don't know the latest information because I don't really follow the issue as I don't run the service mode of BOINC. I run a local version of BOINC in the /home directory where I have total control and permissions are never an issue.

I think the client from the PPA solves this common problem.

You should remove and purge the distro package of BOINC and install the package from the PPA.

---

I've installed that version

~> boinc --version
7.20.5 x86_64-pc-linux-gnu

but it's still doing it:

~> tail -f /var/log/syslog | grep boinc
Feb 11 10:39:21 shuttle boinc[1918]: Authorization required, but no authorization protocol specified
Feb 11 10:39:29 shuttle boinc[1918]: message repeated 17 times: [ Authorization required, but no authorization protocol specified]
Feb 11 10:39:30 shuttle boinc[1918]: Authorization required, but no authorization protocol specified
Feb 11 10:39:30 shuttle boinc[1918]: Authorization required, but no authorization protocol specified
Feb 11 10:39:31 shuttle boinc[1918]: Authorization required, but no authorization protocol specified

Where is that keyword 'shuttle' coming from? It's not used in any BOINC program (I've checked the source code).

And what is trying to talk to what, without authorisation?

Note (for anyone who has read the earlier thread) this (or the equivalent) occurs with both X and Wayland.

This is a report for X: https://github.com/BOINC/boinc/issues/2256

This is for Wayland(?): https://boinc.berkeley.edu/dev/forum_thread.php?id=14249

My memory is that its a result of the Screen Saver option being included in the build, the running process tries to contact the server to determine the current state (idle detection) but doesn't have the correct credentials.

I build my own but now don't have libxss installed, so this feature doesn't get built in and I no longer get the messages.

I build my own but now don't have libxss installed, so this feature doesn't get built in and I no longer get the messages.

I build my own and do have libxss installed but have never had that message. Would that be because the screensaver isn't built in to the master code which I have been using instead of the released versions?