Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65920 - [boinc] doesn't resume after inactivity period
Attached to Project:
Community Packages
Opened by pezcurrel (pezcurrel) - Saturday, 21 March 2020, 14:31 GMT
Last edited by Toolybird (Toolybird) - Sunday, 16 April 2023, 08:13 GMT
Opened by pezcurrel (pezcurrel) - Saturday, 21 March 2020, 14:31 GMT
Last edited by Toolybird (Toolybird) - Sunday, 16 April 2023, 08:13 GMT
|
Details*** Description ***
BOINC doesn't resume after inactivity period. It's not an idle time detection problem, because with "idle_detection_debug" activated in "Event log options" I get log messages like... 21-Mar-2020 15:09:26 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:26 [---] [idle_detection] idle_time: 57791 21-Mar-2020 15:09:27 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:27 [---] [idle_detection] idle_time: 58794 21-Mar-2020 15:09:28 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:28 [---] [idle_detection] idle_time: 59797 21-Mar-2020 15:09:29 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:29 [---] [idle_detection] idle_time: 60806 21-Mar-2020 15:09:30 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:30 [---] [idle_detection] idle_time: 61809 21-Mar-2020 15:09:31 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:31 [---] [idle_detection] idle_time: 62812 21-Mar-2020 15:09:32 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:32 [---] [idle_detection] idle_time: 63815 21-Mar-2020 15:09:33 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:33 [---] [idle_detection] idle_time: 64818 21-Mar-2020 15:09:34 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:34 [---] [idle_detection] idle_time: 65821 21-Mar-2020 15:09:35 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:35 [---] [idle_detection] idle_time: 66824 21-Mar-2020 15:09:36 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:36 [---] [idle_detection] idle_time: 67827 21-Mar-2020 15:09:37 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:37 [---] [idle_detection] idle_time: 68829 21-Mar-2020 15:09:38 [---] [idle_detection] XSS idle detection succeeded on DISPLAY ':0'. 21-Mar-2020 15:09:38 [---] [idle_detection] idle_time: 69832 *** Steps To Reproduce *** 1. run boinc 2. run boincmgr 3. set "'In use' means mouse/keyboard input in last [x] minutes" to 1 in preferences and save 4. wait 1 minute without touching mouse and keyboard: tasks won't resume (they will still show a "Suspended - computer is in use" status) *** Expected behavior *** BOINC tasks should resume after the inactivity period *** System Information *** - OS: up-to-date Arch Linux with kernel 5.5.10-arch1-1 - BOINC Version: 7.16.5 I filed an issue upstream: https://github.com/BOINC/boinc/issues/3509 |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 16 April 2023, 08:13 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Sunday, 16 April 2023, 08:13 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Comment by Cysioland (Cysioland) -
Monday, 20 April 2020, 09:37 GMT
Upstream supposedly fixed this, but it will be live only from version 8.0 on
Comment by Toolybird (Toolybird) -
Sunday, 16 April 2023, 08:12 GMT
AFAICT from perusing their GitHub, the fixes have already been implemented in 7.xx. Either way, it's an upstream issue.