Running boinc-6.4.5-r2 and I have it setup to stop work when the user is at the computer (i.e. minimum of 3 minutes of inactivity required before work is resumed). However, here on gentoo it does not do that. After rebooting the computer (boinc starts automatically), I usually have to do: /etc/init.d/boinc restart and then it will detect when only the root user is active (I have to be doing something on the command-line) and it will stop work. Keyboard/mouse activity under my normal user account does not cause it to stop/resume work. My windows boinc clients all work properly with the same global settings. Reproducible: Always Steps to Reproduce: 1. Set boinc settings to not work when user is active, set timeout to 3 minutes in global project settings. 2. Start boinc, let it start some unit of work 3. Do something with keyboard mouse Actual Results: Nothing. Boinc continues work. Expected Results: Boinc stops work and only resumes after 3 minutes of user inactivity.
It seems that this may be an upstream bug. See: http://boinc.berkeley.edu/trac/ticket/463. However, they do not have a gentoo machine to test on, so perhaps gentoo devs can aid in the debugging/fixing of this bug, at least on gentoo systems?
I have a similar problem with one of my installations, but slightly different, because sometimes the process starts and never stops or never starts at all, even after many hours. At the opposite, my laptop with a fresh install (last month) works perfectly. I really don't understand the difference because both are up-to-date with KDE 3.5.10 ...
Bump. Are any of the boinc maintainers even going to acknowledge this? This is a real problem and no one from the gentoo boinc herd seems to care.
The truth is unfortunately that there are to many packages and too few devs :( Scarabeus is also currently away for quite a while, so he's not likely to much at the moment. I'm currently working on setting up a boinc server, and when I'm done, I _might_ decide I'd like a never client. Then I will try to get us bumped to 6.6. Possibly that will resolve this problem. That's not much, but perhaps it will give some hope to sufferers. :)
newer, client, that is.
Yeah, figured as much. :( I'd love to help, just no time and these days I just need something that works (...wondering if I hear another distro calling my name for that reason alone...).
This seems like it is working with 6.12.26. Please fill the bug upstream if the behaviour is still broken for you.
I just tested it, it still doesn't work. This bug is not FIXED.
