Posts by crashtech

1) Message boards : Questions and problems : Trouble Installing BOINC on Mint 21 (Message 114329)
Posted 2 days ago by crashtech
Post:
Please disregard, the new version did install at some point but perhaps the old one was still in memory, even though I had purged the old version. A simple reboot fixed the problem.
2) Message boards : Questions and problems : Trouble Installing BOINC on Mint 21 (Message 114328)
Posted 2 days ago by crashtech
Post:
Here is the version:
NAME="Linux Mint"
VERSION="21 (Vanessa)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 21"
VERSION_ID="21"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=vanessa
UBUNTU_CODENAME=jammy

I will try again with the instructions for Ubuntu 22.04 when I have a moment, and document the outputs of each command more thoroughly.
3) Message boards : Questions and problems : Trouble Installing BOINC on Mint 21 (Message 114325)
Posted 2 days ago by crashtech
Post:
Here's what I get when following the directions outlined on this page: https://boinc.berkeley.edu/linux_install.php?os_num=4&build=stable

# sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 40254C9B29853EA6
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.MsGFypOXmZ/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv 40254C9B29853EA6
gpg: key 40254C9B29853EA6: "Vitalii Koshura (BOINC DEB and RPM repos key) <lestat.de.lionkur@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

If I then follow the rest of the instructions, an old version of BOINC gets re-installed, presumably because the repository was not properly added.
4) Message boards : BOINC Manager : Any way to set the Default back to Save and Not Cancel (Message 87748)
Posted 21 Aug 2018 by crashtech
Post:
This behavior is occurring on about one in ten of my clients. I'm wondering if there might be some sort of workaround until the next release presumably fixes it? It's really the inconsistency that's the problem for me, if they were all like that, I'd adapt quicker.



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.