Ubuntu
boinc package

Boinc Manager (Pre-Release) Daemon Start failure:

Bug #1975340 reported by Ace Hanna
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
boinc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 22.04 LTS running Boinc 7.18.1+dfsg-4 problems. 1st. after install starting the Boinc client error msg. is you do not have access to Var Lib. I corrected that by adding my user id to the Boinc group and changing the ownership of the group in the Boinc-client folder in etc lib. from root to Boinc. After restarting Boinc the next msg. is "Boinc Manager (Pre-Release) Daemon start failure. Then the client and manager disconnect indicated by the icon in the lower right corner of Boinc. I even tried having the boinc daemon start up at IPL and it made no difference I receive the same error msg. Another Ubuntu user in Ubuntu Redit described the same problem and couldn't fix it so his solution was to restore Ubuntu 20.04 and Boinc worked fine again. Is this really a Pre-Release of Boinc, and if so why was it included in a Long Term Support release instead of the current production version of Boinc for linux? Thanks for your help. Cheers, Ace

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: boinc-client 7.18.1+dfsg-4
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 20 19:40:25 2022
InstallationDate: Installed on 2022-05-18 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: boinc
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ace Hanna (zzace-m) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in boinc (Ubuntu):
status: New → Confirmed
Revision history for this message
Douglas Ribas de Mattos (douglasmattos0) wrote :

I have exactly the same issue in my Computer running Ubuntu 22.04

Revision history for this message
Roland Hughes (original-seasoned-geek) wrote :

I have not tried this on Ubuntu 22.04 other than to encounter the problem and quickly switch to a different distro on my BOINC machines. At least Manjaro knows what the problem is. Now if I could just stop it from shutting one machine down.

https://www.logikalsolutions.com/wordpress/uncategorized/boinc-on-majaro/

Most likely the .DEB "maintainer" is just going through the motions as was the Manjaro packager. The name is now boinc-client.service instead of boinc-client. Read the above link and see if you can get it to start.

I may be spinning 22.04 up on this machine before end of weekend to see if the shutdown is the perpetual Gnome hidden settings problem or not.

Revision history for this message
Samuel Herschbein (cyborgsam) wrote :

Me too: BOINC 7.18.1 Pre-Release in a Ubuntu 22.04 LTS VM in Parallels 18.0.0 on a MacBook Pro 16" M1 Max running Monterey 12.5. All have the most recent updates.

Following these instructions from Roland Hughes' link fixed it for me:
cd /var/lib/boinc
sudo chmod 640 gui_rpc_auth.cfg
sudo chmod o+r gui_rpc_auth.cfg
sudo systemctl enable boinc-client.service
sudo systemctl start boinc-client.service

Revision history for this message
Sergey Serov (druvid) wrote :

Greetings!

I had the same problem. And finally resolved it with these steps:

1). Added myself into boinc group for starting Boinc Manager:

sudo usermod -a -G boinc $(whoami)

2). Added Boinc Client into startup applications:

sudo systemctl enable boinc-client.service

3). Finally reboot system:

reboot

After rebooting both and Manager and Client work. It is necessary to add project and configure application settings.

Revision history for this message
Laurent Lyaudet (laurent-lyaudet) wrote :

Hello :)

I have the same bug on Ubuntu 22.10.
The fix by Sergey Serov above worked for me :)

Best regards,
   Laurent Lyaudet

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.