I have another question. Are you (your username) a member of the boinc group? To check open a terminal and type groups yourusername. For example my username is mark so I would type groups mark.

mark@x32-linux:~$ groups mark
mark : mark adm cdrom sudo dip plugdev lpadmin sambashare boinc

As you can see, I'm a member of the boinc group. If you are not a member then enter the following exact command in a terminal:

sudo usermod -a -G boinc $(whoami)

For it to take effect, you need to log out and log back in.

EDIT: I see this was already suggested by Gregor in a post above.

Looks like I am.

bedrich@bedrich-MS-7599:~$ groups bedrich
bedrich : bedrich adm cdrom sudo dip plugdev lpadmin sambashare boinc

I signed up yesterday, to post my problem.

Hopefully, it can be solved.

I had the same exact problem adding GPUGrid as an existing user to a new remote host during the contest. Same with trying to add Universe.

Was able to use the weak account key just fine to add the project.

Discussion pointed to the change to https in the URLs of those projects not matching the all_projects_list.xml file.

But my situation is different because I use a custom client. Not relevant likely to the OP's problem with a stock client.

In my all_projects_list.xml file, gpugrid, Einstein and milkyway have the https in the url, asteroids has http and I was unable to attach to any of these projects using the weak key method.

I'd like to confirm from reading your original event log dump that you are running Gnome OS.

Is this the true case?

So this was installed as flatpak, correct?

How did you install Boinc? Was it also a flatpak from the Gnome OS distro?

From what I have been reading, Gnome OS is not a true Linux, full-fledged distro.

It is supposed to be nothing more than a testing environment for Gnome. It is not a fully functional Linux distro so probably not expected to behave as a normal distro and probably why you are having issues connecting as an existing project user.

I also believe you installed it in a VM under Windows since I see no indication of a Linux host in your computers list.

Is this the case?

I'd like to confirm from reading your original event log dump that you are running Gnome OS.

Is this the true case?

So this was installed as flatpak, correct?

How did you install Boinc? Was it also a flatpak from the Gnome OS distro?

From what I have been reading, Gnome OS is not a true Linux, full-fledged distro.

It is supposed to be nothing more than a testing environment for Gnome. It is not a fully functional Linux distro so probably not expected to behave as a normal distro and probably why you are having issues connecting as an existing project user.

I also believe you installed it in a VM under Windows since I see no indication of a Linux host in your computers list.

Is this the case?

This is what I installed from this web site, as separate OS on its separate disc :

https://www.linuxmint.com/download.php

Following these instructions:

https://linuxmint-installation-guide.readthedocs.io/en/latest/

I installed boincs through its software manager.

Now, you are telling me that I installed the wrong OS?

What should have I installed instead?

I have not installed Mint in several years but it always identified itself as Mint, not Gnome OS.

Look at your original post of your Event Log. You can see the system identifies itself as Gnome OS. Gnome OS AFAIK is NOT Mint, unless everything has changed in the Mint distro which it probably hasn't.

This is my evidence from your post.

Fri 19 May 2023 10:15:50 PM EDT | | OS: Linux GNOME: GNOME 44 (Flatpak runtime) [5.15.0-72-generic|libc 2.35]

This is the article where I learned what exactly Gnome OS is.

https://itsfoss.com/gnome-os/

I would hope that some other GPUGrid cruncher that is running the Mint distro might chime in with how their Mint installation identifies itself to BOINC.

I know that most often Mint is offered as the closest approximation to Windows UI, but I never had much success with it and went with the most popular distro which is Ubuntu.

Been on Ubuntu since the beginning of my transition from Windows and never had any issues with it. Been rock solid with all applications and projects.

You can look at my two:

Host 132158: Linux Mint 21.1 [5.15.0-71-generic|libc 2.35]
Host 508381: Linux Mint 20.3 [5.4.0-148-generic|libc 2.31]

Both have regular success with both ATM and Python tasks.

This is what I installed from this web site, as separate OS on its separate disc :

https://www.linuxmint.com/download.php

Following these instructions:

https://linuxmint-installation-guide.readthedocs.io/en/latest/

I installed boincs through its software manager.

Now, you are telling me that I installed the wrong OS?

What should have I installed instead?

Mint 21.1 is fine. I have it installed on 4 computers and am running boinc on all of them. I would uninstall the flatpak boinc package via the software manager. I would then suggest adding the Gianfranco Costamagna PPA to your software sources and then installing boinc 7.20.5 by running the following commands:

sudo add-apt-repository ppa:costamagnagianfranco/boinc
sudo apt update
sudo apt install boinc
reboot

Mint 21.1 is fine. I have it installed on 4 computers and am running boinc on all of them. I would uninstall the flatpak boinc package via the software manager. I would then suggest adding the Gianfranco Costamagna PPA to your software sources and then installing boinc 7.20.5 by running the following commands:

sudo add-apt-repository ppa:costamagnagianfranco/boinc
sudo apt update
sudo apt install boinc
reboot

Mint 21.1 is fine, but it isn't (or wasn't?) compatible with PPAs. I installed the PPA on the Mint 20.3 machine, where it loaded properly, and copied the client binary to 21.1

One or other of them may have fixed it since - did you get the PPA to install cleanly on 21.1?

Thanks Richard and biodoc for confirming that Mint identifies as Mint.

I don't know if he actually installed the normal Mint and then installed the flatpak version of Boinc which seemingly changes the way the OS is identifed or what.

I would remove the flatpak version of Boinc and go with the distro's version of Boinc, or the PPA of Gianfranco's.

Mint 21.1 is fine, but it isn't (or wasn't?) compatible with PPAs. I installed the PPA on the Mint 20.3 machine, where it loaded properly, and copied the client binary to 21.1

One or other of them may have fixed it since - did you get the PPA to install cleanly on 21.1?

Now that you mentioned it, I did see a apt-key deprecated warning when I ran apt update but I fixed it using instructions from this link. https://www.omgubuntu.co.uk/2022/06/fix-apt-key-deprecation-error-on-ubuntu

I spent the evening removing and reinstall linux mint. I attempt a manual reinstall of boinc, using the distro's version of Boinc. I believe. The items are in the correct directory. It doesn't seem to work.
Pictures are posted in the link. The OS in linux mint, in case anybody thinks I am making this up, because I am not.

https://github.com/BOINC/boinc/issues/5247


I will make another attempt tomorrow.

Thanks for your effort.

No you are still using the Flatpak version if your posted image is AFTER you supposedly removed BOINC.

sudo apt remove --purge boinc-client boinc-manager

Reboot.

sudo apt install boinc-client boinc-manager

No you are still using the Flatpak version if your posted image is AFTER you supposedly removed BOINC.

sudo apt remove --purge boinc-client boinc-manager

Reboot.

sudo apt install boinc-client boinc-manager

I followed your procedure. Pictures of the results are posted at this link:

https://github.com/BOINC/boinc/issues/5247

Since this site has no drag and drop options, I post the pictures over there. I hope they don't mind.

Therefor it is better to start from as service like systemd. To add it as a service use

sudo systemctl enable boinc-client

To start it

sudo systemctl start boinc-client

To get status

sudo systemctl status boinc-client

You can try set user boinc to folder for read and write

sudo usermod -a -G boinc $USER

and restart computer (re-login should be enough but from experience in past it is forced to restart for this).

@Bedrich Hajek, It looks good so far from what you posted at Github. Now is the time to use the commands above as recommended by @Greger.

Further to that, I would suggest using

sudo systemctl disable boinc-client

before undertaking any form of maintenance, such as kernel updates, that might require a system restart. This prevents BOINC restarting automatically too early in the reboot process, before the video drivers have fully loaded.

Then, when everything is stable, do

sudo systemctl enable boinc-client
sudo systemctl start boinc-client

(in that order) to get things going again.

Now that you mentioned it, I did see a apt-key deprecated warning when I ran apt update but I fixed it using instructions from this link. https://www.omgubuntu.co.uk/2022/06/fix-apt-key-deprecation-error-on-ubuntu

Thanks for that. It seemed to go OK, but I haven't succeeded in getting it to install a refreshed version of the current PPA yet. I'll have another go next time there's something new to install (I'm running v7.20.5 already).

I did this per this morning's post:

https://github.com/BOINC/boinc/issues/5247

Scroll down.

It doesn't seem have gone quite right.

What is the next?

I did this per this morning's post:

https://github.com/BOINC/boinc/issues/5247

Scroll down.

It doesn't seem have gone quite right.

What is the next?

The command you used for adding your username to the boinc group was incorrect. Remove the $ sign from in front of your username in the command you entered or enter the following exactly as typed. $USER is a variable that is your username.

sudo usermod -a -G boinc $USER

Then reboot

I did this:

sudo usermod -a -G boinc bedrichhajek

groups bedrichhajek

rebooted

Then did this again:

sudo systemctl disable boinc-client

sudo systemctl enable boinc-client
sudo systemctl start boinc-client

cd /usr/bin
ls |grep boinc
ls -ail |grep boinc

./boinc

./boincmgr

It look good until the last two steps.

See link for pictures:

https://github.com/BOINC/boinc/issues/5247