BOINC client fails to detect when the system is idle

Bug #1900803 reported by Mauro
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
boinc (Ubuntu)
Fix Released
High
Unassigned
Focal
Confirmed
Undecided
Unassigned
Groovy
Won't Fix
Undecided
Unassigned

Bug Description

[ Impact ]
BOINC client 7.16.6 packaged for Ubuntu 20.04 fails to detect when the system is idle. So, if you set your projects to run after the system has been idle for x minutes, computations will never start and remain in status "Suspended - computer is in use" state forever.

This is a regression compared to older versions (7.16.3 for instance).
Seems to be fixed upstream in 7.16.11, see: https://github.com/BOINC/boinc/issues/3715

[ Test case ]
* Open boinc and set to run only if the system is idle, in syslog you will spot lots of "permission denied" and it won't detect the idle time without starting

[ Regression Potential ]
* Low, the current code looks broken due two bugs, one permission denied issue fixed with a service file change, and the other in the detection code due to a wrong variable being used

[ Other info ]
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: boinc-client 7.16.6+dfsg-1
ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Oct 21 09:17:09 2020
InstallationDate: Installed on 2020-10-05 (15 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: boinc
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.boinc-client.gui_rpc_auth.cfg: [inaccessible: [Errno 13] Permesso negato: '/etc/boinc-client/gui_rpc_auth.cfg']
mtime.conffile..etc.boinc-client.global_prefs_override.xml: 2020-04-22T12:16:59

Revision history for this message
Mauro (mauromol) wrote :
description: updated
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
Changed in boinc (Ubuntu):
importance: Undecided → High
Changed in boinc (Ubuntu):
status: Confirmed → Fix Released
Changed in boinc (Ubuntu Groovy):
status: New → In Progress
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release

Changed in boinc (Ubuntu Groovy):
status: In Progress → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in boinc (Ubuntu Focal):
status: New → Confirmed
Revision history for this message
Gordon P. Hemsley (gphemsley) wrote :

Any word on when this upstream fix might make its way to Focal?

Revision history for this message
Gordon P. Hemsley (gphemsley) wrote :

Note that there appear to be two different patches that need to be incorporated, to fix different underlying causes:
https://github.com/BOINC/boinc/pull/3512
https://github.com/BOINC/boinc/pull/4105

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

Other bug subscribers

Remote bug watches

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