After upgrading to impish (21.10) reverting to the older version from focal
(20.04 LTS) still solves the issue for me.
boinc_7.16.6+dfsg-1_all.deb (from https://packages.ubuntu.com/focal/boinc)
boinc-client_7.16.6+dfsg-1_amd64.deb (from
(https://packages.ubuntu.com/focal/boinc-client)
boinc-manag
In the meanwhile I reverted to the older version from focal:
boinc_7.16.6+dfsg-1_all.deb (from https://packages.ubuntu.com/focal/boinc)
boinc-client_7.16.6+dfsg-1_amd64.deb (from
(https://packages.ubuntu.com/focal/boinc-client)
boinc-manager_7.16.6+dfsg-1_amd64.deb (from
https://packages.ubuntu.c
Latest version of development release fixes this bug -
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc
7.16.15+dfsg.is.7.16.11+dfsg+202011100036~ubuntu20.10.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Try setting the /etc/boinc-client/gui_rpc_auth.cfg to just
boinc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895157
Title:
Boinc cannot enable RPC access to start client or manager
To manage not
Tried the suggestion in comment #9 and that produced the error message
"Invalid client RPC password. Try reinstalling BOINC."
I already did a reinstall using aptitude.
I also found a version of the file at a higher level, but messing with
that one didn't help, either.
--
You received this bug n
All that it took for me was to put any text in /etc/boinc-
client/gui_rpc_auth.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895157
Title:
Boinc cannot enable RPC access to start client or mana
The minimal solution of comment #4 did not work for me. I also tried
manually changing the permissions of the file to make it "Read and
write", but I didn't look for the BOINC group, so I'm going to try that
next...
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Actually this does seem to be a recent change
-https://github.com/BOINC/boinc/issues/4021 as the other debian bug
you've found mentions to.
** Bug watch added: github.com/BOINC/boinc/issues #4021
https://github.com/BOINC/boinc/issues/4021
--
You received this bug notification because you are
This bug specifically references a case where the password is created
properly. The password that auto generates oui r is put in manually is
inaccessible by the boinc manager. This is due to it being owned by root
and only viewable by the boinc group. The boinc client is run under the
boinc usern
** Changed in: boinc (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895157
Title:
Boinc cannot enable RPC access to start client or manager
To manage notifica
This seems really similar to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=720849 but I just realized that was from 6 years
ago..
** Bug watch added: Debian Bug tracker #720849
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720849
** Also affects: boinc (Debian) via
https://bugs.deb
I had the same problem in Ubuntu 20.10 and was able to get boinc working
again by doing the following:
1. Stop boinc service and kill any boinc processes
2. Remove the gui_rpc_auth.cfg from /etc/boinc (It would probably be safer to
change its name to gui_rpc_auth.cfg.old or something.)
3. Rebo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: boinc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895157
Title:
Boin
By manually extracting the password from the file in /etc/boinc-client
and entering it into Boinc Manager does connect it to the client. So
this might be a minor configuration issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Some research unearthed a reason and possible solution -
This error happens when the user has no permission to use the RPC port number,
or forgotten to allow it through the firewall.
Happens in combination with Gstate.init() failed, error code: -180
To set BOINC to use a specific port number, on
15 matches
Mail list logo
