Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2015-12-16 Thread Preston Maness 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Howdy howdy,

I have a pull request with upstream now:

https://github.com/BOINC/boinc/pull/1453

And I've attached a patch against upstream's master as of this morning
(HEAD 1ca5f51cc7c993799f27d99bfa871d57567a30e5).

I'm not an autotools whiz, so I don't know if the changes I made to
configure.ac --mostly pulled from the commit that originally deleted
them, but I added a small flag when building the client so that the
original commit's checks are actually run-- are ideal, or if the
changes made are suitable for an automatic detection of new
dependencies. I'm starting to learn about package management a la
git-buildpackage, but I've got a ways to go.

Cheers,
Preston

P.S. - It looks like there's another bug from January 2015 that's
essentially a dupe of this one. Hopefully both can be closed soon :D

On 12/16/2015 01:16 AM, Gianfranco Costamagna wrote:
> Hi if you can give me a patch for the source code and submit a pull
> request upstream (github), I can find with git log the configure.ac
> patches, add the Debian dependencies again and reupload on
> unstable. Thanks G.
> 
> Sent from Yahoo Mail on Android
> 
> On Wed, 16 Dec, 2015 at 0:34, Preston
> Maness wrote:   -BEGIN PGP SIGNED
> MESSAGE- Hash: SHA512
> 
> An update:
> 
> Re-incorporating the XSS idle-detection code works as expected. I 
> scrapped the DPMS code and only kept the XSS code. Inclusion of
> 
> #include 
> 
> in "client/hostinfo_unix.cpp" ultimately pulls in a conflicting 
> definition of "Always" between X-related code and boinc's 
> "lib/prefs.h", fixed by renaming boinc's declaration. After this,
> the boinc-client and boincmgr compile and idle detection works as
> expected (keyboard and mouse inputs are appropriately detected, and
> computation is suspended).
> 
> Working on cleaning up the changes, hopefully getting upstream to 
> reinstate the XSS code, and determining how best to get the fix
> into the Debian packages. From what I can tell, an additional
> dependency on "libxss1" would be necessary.
> 
> Cheers, Preston
> 
> On 12/14/2015 07:28 AM, Preston Maness wrote:
>> Whelp, it looks like the X-based idle detection --with the 
>> XScreenSaver API?-- was removed in this commit:
>> 
>> ==
>> 
>> bfae1032e5c1ac73f2d8d92f93d8383a6cee
>> 
>> https://github.com/BOINC/boinc/commit/bfae1032e5c1ac73f2d8d92f93d
8
>
>> 
38
>> 
>> 
> 3a6cee
>> 
>> ==
>> 
>> The commit message indicates that /dev/input/* devices are the 
>> intended way to determine idle time on Linux now. However, it 
>> seems that X-based inputs don't update the /dev/input/* devices.
>> Or at least, anything the X server is doing isn't updating the
>> atime on those files, which is what is being utilized to
>> determine if the system is idle or not. Working in a terminal
>> updates the atime on the relevant files --correctly triggering
>> BOINC to suspend computation-- but just typing this email, or
>> wiggling the mouse around the desktop area, doesn't.
>> 
>> Granted, this code was present earlier, so I don't know if simply
>>  re-introducing it will solve anything. But that's my first plan
>> of attack. I've also looked into other varying methods of idle 
>> detection. The XSS API is the most common, but there is a more 
>> convoluted (asynchronous?) Xsync option that might also be
>> possible too. I don't know too much about X, but I'll be giving a
>> few different possibilities a go in the coming days.
>> 
>> Cheers, Preston
>> 
>> On 12/11/2015 09:44 AM, Preston Maness wrote:
>>> Howdy howdy,
>> 
>>> I think I deserve a slow clap for such a slow 
>>> response/addresssing of a bug. Indeed my response is so slow
>>> that I've since changed email address and GPG keys.
>> 
>>> Needless to say, when running BOINC 7.6.12 from testing, some 
>>> progress seems to have been made on idle detection. If I open a
>>>  terminal and begin working in it, *sometimes*, the idle
>>> detection kicks in. I can't tell whether it's working as
>>> intended or not. Regardless, keeping boinc running non-stop
>>> doesn't pose any issues thanks to the scheduling. I can happily
>>> use my machine for just about anything and not even notice that
>>> BOINC is running.
>> 
>>> I'm presently unemployed, so really, I have nothing but time
>>> and no real excuses not to give this bug another go and see if
>>> I can just determine once and for all if things are fixed/how
>>> to fix them :P
>> 
>>> It looks like the BOINC project has moved from their own git 
>>> infrastructure onto github:
>> 
>>> https://boinc.berkeley.edu/trac/wiki/SourceCodeGit
>> 
>>> https://github.com/BOINC/boinc
>> 
>>> Looking at the git log for hostinfo_unix.cpp (a la "git log 
>>> client/hostinfo_unix.cpp" from the project root), it looks like
>>>  there was a commit that included changes from Gianfranco:
>> 
>>> ==
>> 
>>> commit 0811886cbb1d282376e2dfd017ab39e34cd7d8ea Author:

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2015-12-15 Thread Preston Maness 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

An update:

Re-incorporating the XSS idle-detection code works as expected. I
scrapped the DPMS code and only kept the XSS code. Inclusion of

#include 

in "client/hostinfo_unix.cpp" ultimately pulls in a conflicting
definition of "Always" between X-related code and boinc's
"lib/prefs.h", fixed by renaming boinc's declaration. After this, the
boinc-client and boincmgr compile and idle detection works as expected
(keyboard and mouse inputs are appropriately detected, and computation
is suspended).

Working on cleaning up the changes, hopefully getting upstream to
reinstate the XSS code, and determining how best to get the fix into
the Debian packages. From what I can tell, an additional dependency on
"libxss1" would be necessary.

Cheers,
Preston

On 12/14/2015 07:28 AM, Preston Maness wrote:
> Whelp, it looks like the X-based idle detection --with the 
> XScreenSaver API?-- was removed in this commit:
> 
> ==
> 
> bfae1032e5c1ac73f2d8d92f93d8383a6cee
> 
> https://github.com/BOINC/boinc/commit/bfae1032e5c1ac73f2d8d92f93d8
38
>
> 
3a6cee
> 
> ==
> 
> The commit message indicates that /dev/input/* devices are the 
> intended way to determine idle time on Linux now. However, it
> seems that X-based inputs don't update the /dev/input/* devices. Or
> at least, anything the X server is doing isn't updating the atime
> on those files, which is what is being utilized to determine if
> the system is idle or not. Working in a terminal updates the atime
> on the relevant files --correctly triggering BOINC to suspend
> computation-- but just typing this email, or wiggling the mouse
> around the desktop area, doesn't.
> 
> Granted, this code was present earlier, so I don't know if simply 
> re-introducing it will solve anything. But that's my first plan of 
> attack. I've also looked into other varying methods of idle
> detection. The XSS API is the most common, but there is a more
> convoluted (asynchronous?) Xsync option that might also be possible
> too. I don't know too much about X, but I'll be giving a few
> different possibilities a go in the coming days.
> 
> Cheers, Preston
> 
> On 12/11/2015 09:44 AM, Preston Maness wrote:
>> Howdy howdy,
> 
>> I think I deserve a slow clap for such a slow
>> response/addresssing of a bug. Indeed my response is so slow that
>> I've since changed email address and GPG keys.
> 
>> Needless to say, when running BOINC 7.6.12 from testing, some 
>> progress seems to have been made on idle detection. If I open a 
>> terminal and begin working in it, *sometimes*, the idle detection
>>  kicks in. I can't tell whether it's working as intended or not.
>>  Regardless, keeping boinc running non-stop doesn't pose any
>> issues thanks to the scheduling. I can happily use my machine for
>> just about anything and not even notice that BOINC is running.
> 
>> I'm presently unemployed, so really, I have nothing but time and
>> no real excuses not to give this bug another go and see if I can
>> just determine once and for all if things are fixed/how to fix
>> them :P
> 
>> It looks like the BOINC project has moved from their own git 
>> infrastructure onto github:
> 
>> https://boinc.berkeley.edu/trac/wiki/SourceCodeGit
> 
>> https://github.com/BOINC/boinc
> 
>> Looking at the git log for hostinfo_unix.cpp (a la "git log 
>> client/hostinfo_unix.cpp" from the project root), it looks like 
>> there was a commit that included changes from Gianfranco:
> 
>> ==
> 
>> commit 0811886cbb1d282376e2dfd017ab39e34cd7d8ea Author: David 
>> Anderson  Date:   Mon Feb 3 12:46:43 2014
>>  -0800
> 
>> client: fix for idle detection on Linux (from Gianfranco)
> 
> 
>> ==
> 
>> and some later refactoring of the unix HOSTINFO code:
> 
>> ==
> 
>> commit cda6bd334bf036349f471a0c4eb7c25de8098262 Author: David 
>> Anderson  Date:   Tue Nov 25 14:46:58
>> 2014 -0800
> 
>> client: get static host info items only on startup
> 
>> On Android, the way we were getting os_version (Linux version + 
>> Android version) didn't work because get_host_info() was getting
>>  called before every scheduler RPC, and it overwrote the Android
>>  version part.
> 
>> Solution: divide host info into dynamic (disk usage, network
>> info) and static (everything else). Computer the static part only
>> at startup.
> 
>> Also factor the Unix HOST_INFO code into multiple functions.
> 
>> ==
> 
>> As it stands, BOINC's Event Log does show periodic "Suspending 
>> computation - computer is in use" messages. Show I'm operating on
>>  the assumption that something is working.
> 
>> Cheers, Preston Maness
> 
> 
> 

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJWcKN0AAoJEFpzcfOOuHp0vY8QAM21NXoSO0S73rsL5Ci5WEZL
D2RbjefCRb+ojSGCFRtRG8fnLVS88P9Kyj5EfwvQPzQhHIsv2aZCfvl3JkPz49A0
khjaKr7DxgM2DtCxkTbq6HNeYtyr2YQounyZdhEOn/vYp4SmeOVxgC/2j31WYY95

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2015-12-15 Thread Gianfranco Costamagna 
Hi if you can give me a patch for the source code and submit a pull request 
upstream (github), I can find with git log the configure.ac patches, add the 
Debian dependencies again and reupload on unstable.
Thanks
G.

Sent from Yahoo Mail on Android 
 
  On Wed, 16 Dec, 2015 at 0:34, Preston Maness wrote: 
  -BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

An update:

Re-incorporating the XSS idle-detection code works as expected. I
scrapped the DPMS code and only kept the XSS code. Inclusion of

#include 

in "client/hostinfo_unix.cpp" ultimately pulls in a conflicting
definition of "Always" between X-related code and boinc's
"lib/prefs.h", fixed by renaming boinc's declaration. After this, the
boinc-client and boincmgr compile and idle detection works as expected
(keyboard and mouse inputs are appropriately detected, and computation
is suspended).

Working on cleaning up the changes, hopefully getting upstream to
reinstate the XSS code, and determining how best to get the fix into
the Debian packages. From what I can tell, an additional dependency on
"libxss1" would be necessary.

Cheers,
Preston

On 12/14/2015 07:28 AM, Preston Maness wrote:
> Whelp, it looks like the X-based idle detection --with the 
> XScreenSaver API?-- was removed in this commit:
> 
> ==
> 
> bfae1032e5c1ac73f2d8d92f93d8383a6cee
> 
> https://github.com/BOINC/boinc/commit/bfae1032e5c1ac73f2d8d92f93d8
38
>
> 
3a6cee
> 
> ==
> 
> The commit message indicates that /dev/input/* devices are the 
> intended way to determine idle time on Linux now. However, it
> seems that X-based inputs don't update the /dev/input/* devices. Or
> at least, anything the X server is doing isn't updating the atime
> on those files, which is what is being utilized to determine if
> the system is idle or not. Working in a terminal updates the atime
> on the relevant files --correctly triggering BOINC to suspend
> computation-- but just typing this email, or wiggling the mouse
> around the desktop area, doesn't.
> 
> Granted, this code was present earlier, so I don't know if simply 
> re-introducing it will solve anything. But that's my first plan of 
> attack. I've also looked into other varying methods of idle
> detection. The XSS API is the most common, but there is a more
> convoluted (asynchronous?) Xsync option that might also be possible
> too. I don't know too much about X, but I'll be giving a few
> different possibilities a go in the coming days.
> 
> Cheers, Preston
> 
> On 12/11/2015 09:44 AM, Preston Maness wrote:
>> Howdy howdy,
> 
>> I think I deserve a slow clap for such a slow
>> response/addresssing of a bug. Indeed my response is so slow that
>> I've since changed email address and GPG keys.
> 
>> Needless to say, when running BOINC 7.6.12 from testing, some 
>> progress seems to have been made on idle detection. If I open a 
>> terminal and begin working in it, *sometimes*, the idle detection
>>  kicks in. I can't tell whether it's working as intended or not.
>>  Regardless, keeping boinc running non-stop doesn't pose any
>> issues thanks to the scheduling. I can happily use my machine for
>> just about anything and not even notice that BOINC is running.
> 
>> I'm presently unemployed, so really, I have nothing but time and
>> no real excuses not to give this bug another go and see if I can
>> just determine once and for all if things are fixed/how to fix
>> them :P
> 
>> It looks like the BOINC project has moved from their own git 
>> infrastructure onto github:
> 
>> https://boinc.berkeley.edu/trac/wiki/SourceCodeGit
> 
>> https://github.com/BOINC/boinc
> 
>> Looking at the git log for hostinfo_unix.cpp (a la "git log 
>> client/hostinfo_unix.cpp" from the project root), it looks like 
>> there was a commit that included changes from Gianfranco:
> 
>> ==
> 
>> commit 0811886cbb1d282376e2dfd017ab39e34cd7d8ea Author: David 
>> Anderson  Date:  Mon Feb 3 12:46:43 2014
>>  -0800
> 
>> client: fix for idle detection on Linux (from Gianfranco)
> 
> 
>> ==
> 
>> and some later refactoring of the unix HOSTINFO code:
> 
>> ==
> 
>> commit cda6bd334bf036349f471a0c4eb7c25de8098262 Author: David 
>> Anderson  Date:  Tue Nov 25 14:46:58
>> 2014 -0800
> 
>> client: get static host info items only on startup
> 
>> On Android, the way we were getting os_version (Linux version + 
>> Android version) didn't work because get_host_info() was getting
>>  called before every scheduler RPC, and it overwrote the Android
>>  version part.
> 
>> Solution: divide host info into dynamic (disk usage, network
>> info) and static (everything else). Computer the static part only
>> at startup.
> 
>> Also factor the Unix HOST_INFO code into multiple functions.
> 
>> ==
> 
>> As it stands, BOINC's Event Log does show periodic "Suspending 
>> computation - computer is in use" messages. Show I'm

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2015-12-14 Thread Preston Maness 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Whelp, it looks like the X-based idle detection --with the
XScreenSaver API?-- was removed in this commit:

==

bfae1032e5c1ac73f2d8d92f93d8383a6cee

https://github.com/BOINC/boinc/commit/bfae1032e5c1ac73f2d8d92f93d838
3a6cee

==

The commit message indicates that /dev/input/* devices are the
intended way to determine idle time on Linux now. However, it seems
that X-based inputs don't update the /dev/input/* devices. Or at
least, anything the X server is doing isn't updating the atime on
those files, which is what is being utilized to determine if the
system is idle or not. Working in a terminal updates the atime on the
relevant files --correctly triggering BOINC to suspend computation--
but just typing this email, or wiggling the mouse around the desktop
area, doesn't.

Granted, this code was present earlier, so I don't know if simply
re-introducing it will solve anything. But that's my first plan of
attack. I've also looked into other varying methods of idle detection.
The XSS API is the most common, but there is a more convoluted
(asynchronous?) Xsync option that might also be possible too. I don't
know too much about X, but I'll be giving a few different
possibilities a go in the coming days.

Cheers,
Preston

On 12/11/2015 09:44 AM, Preston Maness wrote:
> Howdy howdy,
> 
> I think I deserve a slow clap for such a slow response/addresssing 
> of a bug. Indeed my response is so slow that I've since changed 
> email address and GPG keys.
> 
> Needless to say, when running BOINC 7.6.12 from testing, some 
> progress seems to have been made on idle detection. If I open a 
> terminal and begin working in it, *sometimes*, the idle detection 
> kicks in. I can't tell whether it's working as intended or not. 
> Regardless, keeping boinc running non-stop doesn't pose any issues 
> thanks to the scheduling. I can happily use my machine for just 
> about anything and not even notice that BOINC is running.
> 
> I'm presently unemployed, so really, I have nothing but time and no
> real excuses not to give this bug another go and see if I can just
> determine once and for all if things are fixed/how to fix them :P
> 
> It looks like the BOINC project has moved from their own git 
> infrastructure onto github:
> 
> https://boinc.berkeley.edu/trac/wiki/SourceCodeGit
> 
> https://github.com/BOINC/boinc
> 
> Looking at the git log for hostinfo_unix.cpp (a la "git log 
> client/hostinfo_unix.cpp" from the project root), it looks like 
> there was a commit that included changes from Gianfranco:
> 
> ==
> 
> commit 0811886cbb1d282376e2dfd017ab39e34cd7d8ea Author: David 
> Anderson  Date:   Mon Feb 3 12:46:43 2014 
> -0800
> 
> client: fix for idle detection on Linux (from Gianfranco)
> 
> 
> ==
> 
> and some later refactoring of the unix HOSTINFO code:
> 
> ==
> 
> commit cda6bd334bf036349f471a0c4eb7c25de8098262 Author: David 
> Anderson  Date:   Tue Nov 25 14:46:58 2014 
> -0800
> 
> client: get static host info items only on startup
> 
> On Android, the way we were getting os_version (Linux version + 
> Android version) didn't work because get_host_info() was getting 
> called before every scheduler RPC, and it overwrote the Android 
> version part.
> 
> Solution: divide host info into dynamic (disk usage, network info)
>  and static (everything else). Computer the static part only at 
> startup.
> 
> Also factor the Unix HOST_INFO code into multiple functions.
> 
> ==
> 
> As it stands, BOINC's Event Log does show periodic "Suspending 
> computation - computer is in use" messages. Show I'm operating on 
> the assumption that something is working.
> 
> Cheers, Preston Maness
> 

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJWbsPqAAoJEFpzcfOOuHp0f4oP/i1doHmk9oEtCfOB/k1T9KXJ
CQSDQiaBK1K1btEKi7jN7vhff6nXZx0km/Cr5g2rDjb9fQwJ15Myxk9cRQq69+Nu
13U6DyZd4ZWj+TsoaaSH2kQKW4E7jtTUTz0PFapC6Q2x7YgngMnIC1ubsW3vQpkk
pdOkOpxu2W1X/JhTIlMnFiARRLYIPzSkh7W0/IXHwTROxNkFpZTWhhv3hgkv20A8
ymfGe5URIIZlbbppan04iTwWFrdBNB2WZOWKM1U018KqHc5umfReWjXYdmYN6K4D
gVKFfoM+cSyKFty82bhzZ69aRvjwNQb86lmTXGKAl0fz5nLy2WA43kyV0V9KSnWE
/byLgHfzrO8crS7tsd8V0e8O3gsXvPNGsvKuDJtnfLYyOKF8q6vopARblfeGglTS
NSi3iGfrAXwbr6cLeHYZHb46XVUOk7IdjrsjP69NtKBeqKJxvcqCtcZjK3rk2ljU
9+IDBIkmC/fnVGBUcCWul7wrTklrXPMmYIS4UksBmcgQ2FSCq75QgOfQ05kL9Wai
QbWLDbCtfKLSoh+6uxc7iRIuvQNrtdvwKzJCoZdlMxsD0hiOGW3WOypg8caORWE2
2McfFmJBvXgFbQU0610UTBolyv9P0IRaMgdNQW+gM2V7HuYmUA2Nsmof/E7F/9vO
Kp3tGDm6su9HG/ihtOlE
=VPvD
-END PGP SIGNATURE-

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2015-12-11 Thread Preston Maness 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Howdy howdy,

I think I deserve a slow clap for such a slow response/addresssing of
a bug. Indeed my response is so slow that I've since changed email
address and GPG keys.

Needless to say, when running BOINC 7.6.12 from testing, some progress
seems to have been made on idle detection. If I open a terminal and
begin working in it, *sometimes*, the idle detection kicks in. I can't
tell whether it's working as intended or not. Regardless, keeping
boinc running non-stop doesn't pose any issues thanks to the
scheduling. I can happily use my machine for just about anything and
not even notice that BOINC is running.

I'm presently unemployed, so really, I have nothing but time and no
real excuses not to give this bug another go and see if I can just
determine once and for all if things are fixed/how to fix them :P

It looks like the BOINC project has moved from their own git
infrastructure onto github:

https://boinc.berkeley.edu/trac/wiki/SourceCodeGit

https://github.com/BOINC/boinc

Looking at the git log for hostinfo_unix.cpp (a la "git log
client/hostinfo_unix.cpp" from the project root), it looks like there
was a commit that included changes from Gianfranco:

==

commit 0811886cbb1d282376e2dfd017ab39e34cd7d8ea
Author: David Anderson 
Date:   Mon Feb 3 12:46:43 2014 -0800

client: fix for idle detection on Linux (from Gianfranco)


==

and some later refactoring of the unix HOSTINFO code:

==

commit cda6bd334bf036349f471a0c4eb7c25de8098262
Author: David Anderson 
Date:   Tue Nov 25 14:46:58 2014 -0800

client: get static host info items only on startup

On Android, the way we were getting os_version
(Linux version + Android version)
didn't work because get_host_info() was getting called before every
scheduler RPC, and it overwrote the Android version part.

Solution: divide host info into dynamic (disk usage, network info)
and static (everything else).
Computer the static part only at startup.

Also factor the Unix HOST_INFO code into multiple functions.

==

As it stands, BOINC's Event Log does show periodic "Suspending
computation - computer is in use" messages. Show I'm operating on the
assumption that something is working.

Cheers,
Preston Maness
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJWau80AAoJEFpzcfOOuHp0b5gQAI0yCYXWOrljUJDwn1cTtjPx
CPADEHJTf9FD4vy52wJzrTHdtvq3nj9ihaF+MCkYZvbIwndtabku1JyqahQd29uW
XUw4i8cE99FWQE66FJk8PIk5UgvY01y9h/B709B2rwXq02rtbo0YjOCWTpQnD1Xl
eTA3Nj97PLfw7i/2LJuD6BOUsPL9NNzjbqwPRdzKdipR7DQn4HrykKqe78VGspIz
POTOLqhv4x6BOaKRp+uxgI19Zb1THlaAYH6drw07mgYlxwO6NePfB1fC8Uqeusot
6O1UOdaQ4OiIhZ0tAouzzOCk3944NvxY1Zrg3XQl8UxxAfjSM/8uCygUETw5OZvi
qQC9CrkXeSjfiqIUnHzR3JQMvr+YdPP3pWi9NpqcEv73Rty8GZ9OXvCVNMu3dRk0
Flpu7PSUz79s6u6YlFKzMc97JU1ZtDeWlAK2zx8QZbQDr8uFRZK/YDNspz/WBmwR
lAVErCEfi4yPYdKxHtfbZKcz0LVKAo5hw8szBxciLLYkbz0i/XVguEO7/HgD0G/r
9pmhPg+698ftyZ2Er2/zufYFHw2sYY5qIKR+yg3RUK1fKO3ayO/iflycwfh7poKU
SHBroRxdsE5WWAe4FH1lMNmMkLNH0RQBKjcm7V2gaMGpG38Pvow8glzlBH5DYjOZ
cmMcv0aRUpXLPeiolQO/
=q0tn
-END PGP SIGNATURE-

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-10-30 Thread Preston Maness 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Greetings,

 Could you check if you have libxcb-dpms0 package installed? I
 suspect that this is related to the idle-time function in boinc,
 and this library didn't end up into boinc-client's dependency
 because it functions as a plugin...

 Try to run boinc-client without those constant-updating-terminal 
 programs, and see if there's any difference.

I did have terminals that were updating regularly. And I didn't have
the libxcb-dpms0 package installed. I've turned off the terminals and
installed the package. I set the idle time to 0.5 minutes, and
restarted boinc-client. After several minutes, the program still
claims to detect user activity.

Thanks for listing the relevant code. I'm going to have a look at it
over the weekend and see if I can't at least figure out a way to log
what precisely is being detected. I suspect that attempting to
live-debug with gdb could get hairy, though I could always dive into
that if I had to.

Cheers,
Preston Maness
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJSca7oAAoJEM8h7WmSAmadisoH/3ETae38BHZDEgU3/eEQyyHL
Ap+m62liRbmHZtiCp0wXrozLw73e5TseKFIY2KjxQqqqbugediUYbSbcs/M7vap9
83a0VvwTbkjdPUelnK3Uv1kRrGiGGBzPtVvFLc74Xq611m2tTsjwycp4whtf9E4d
VynhuqesVXg//tc87pxFdq6pcehBogmC7RjGzROAxbZZ0OHDP57mL47P5c8w41TL
7peFB4k5aL0WJ0EiTI75WmyID1MixbDGLI1+XiVCzF5atOyVNCnckB7+MDACqZn4
uaKVdt/xuEix+DfLCNzNe31vwp9bqn1w439uQKfXtbPKjwA2B2hddzMhCe4ycAY=
=wSDr
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-10-30 Thread GUO Yixuan 
Hello,

On Wed, Oct 30, 2013 at 08:14:24PM -0500, Preston Maness wrote:
  Could you check if you have libxcb-dpms0 package installed? I
  suspect that this is related to the idle-time function in boinc,
  and this library didn't end up into boinc-client's dependency
  because it functions as a plugin...
 
  Try to run boinc-client without those constant-updating-terminal 
  programs, and see if there's any difference.
 
 I did have terminals that were updating regularly. And I didn't have
 the libxcb-dpms0 package installed. I've turned off the terminals and
 installed the package. I set the idle time to 0.5 minutes, and
 restarted boinc-client. After several minutes, the program still
 claims to detect user activity.
 
 Thanks for listing the relevant code. I'm going to have a look at it
 over the weekend and see if I can't at least figure out a way to log
 what precisely is being detected. I suspect that attempting to
 live-debug with gdb could get hairy, though I could always dive into
 that if I had to.
 
 Cheers,
 Preston Maness

A way of non-intrusive debugging is to use printf. I've used
msg_printf(), which can print message to stdoutdae.txt in
stdoutdae.txt, or the event log in boincmgr. (Therefore I am able to
debug even if boinc is in the normal daemon mode.)

Cheers,

Yixuan


signature.asc
Description: Digital signature

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-10-29 Thread GUO Yixuan 
Control: tag -1 + upstream

Hi,

On Sun, Oct 27, 2013 at 11:39:28AM -0400, GUO Yixuan wrote:
 On Sat, Aug 31, 2013 at 03:14:43AM -0500, Preston Maness wrote:
  Snippet from log file:
  
   31-Aug-2013 03:02:40 Initialization completed 31-Aug-2013 03:02:40
   [---] Suspending computation - computer is in use
  
  After several minutes, the logs at /var/lib/boinc-client/stdoutdae.txt
  still only state that the computer is in use. Network activity
  continues of course, as per the xml file with the settings. But no CPU
  or GPU activity.
  
  Is there perhaps a log of the activity that boinc is supposedly
  detecting? I suspect there could be a background process of some sort
  on my machine that is being detected as active user activity, leading
  boinc to believe the computer is in use. But I can't find any logs
  that look relevant in /var/lib/boinc-client/.
 
 Could you check if you have libxcb-dpms0 package installed? I suspect
 that this is related to the idle-time function in boinc, and this
 library didn't end up into boinc-client's dependency because it
 functions as a plugin...

There's another possibility: do you use tmux or screen with a clock in
its status bar, or do you use some system monitor program that runs in a
tty or pts (term emulator), and that is constantly updating? (such as
top or htop)

I just investigated boinc-client's idle detection function, which is
pretty complexed, and it checks all tty and pts's atime as a step,
beside mouse and keyboard timestamps from kernel and X11.

Try to run boinc-client without those constant-updating-terminal
programs, and see if there's any difference.

(Actually this idle detection function is not quite satisfactory, imo ...)

The relevent code is in client/hostinfo_unix.cpp, in the function
bool HOST_INFO::users_idle() (notice that the first one is for apple,
and the other is for linux/unix-like)

Cheers,

GUO Yixuan


signature.asc
Description: Digital signature

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-10-27 Thread GUO Yixuan 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

On Sat, Aug 31, 2013 at 03:14:43AM -0500, Preston Maness wrote:
 Greetings,
 
  computation should start after 20 seconds of inactivity or
  something like that thanks
 
 Snippet from log file:
 
  31-Aug-2013 03:02:40 Initialization completed 31-Aug-2013 03:02:40
  [---] Suspending computation - computer is in use
 
 After several minutes, the logs at /var/lib/boinc-client/stdoutdae.txt
 still only state that the computer is in use. Network activity
 continues of course, as per the xml file with the settings. But no CPU
 or GPU activity.
 
 Is there perhaps a log of the activity that boinc is supposedly
 detecting? I suspect there could be a background process of some sort
 on my machine that is being detected as active user activity, leading
 boinc to believe the computer is in use. But I can't find any logs
 that look relevant in /var/lib/boinc-client/.

Could you check if you have libxcb-dpms0 package installed? I suspect
that this is related to the idle-time function in boinc, and this
library didn't end up into boinc-client's dependency because it
functions as a plugin...

Cheers,

GUO Yixuan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCgAGBQJSbTOwAAoJEN1xpgAgL7gz7JgQAImli1wLBhnNAVo1Wyf/obM/
dtVIRndHUyeog4EOq2NsvHm46CPY3UG1okYJMrb4QC5+MsJqyh13A9/z25dN5gFt
RxI7/Yw6eXxiWXQJb72cDmHpr9UzA9JWUc/xlGtDxP0jC0NHZevNMjFp6B9odM/A
lFjJ/mnX0c9DSullLbscTl2bNZRC2HluG6l++lrx2TbOSkzm+GStUBlo/ce+VvhI
dr2kH3FPmTC5WFNymUYTHqe2/lvqCtA9kTZgUy0Gsr1V2tGtF67WV3XcNuuCD4k3
filSCers259b7x5tPkg9kH16Z4fMGN+LhSuHE9Gjgz5IdMYqT2l/K2FD9JMWIJZS
YMU7UxgOJGmxs95WS1jMPxI3nr0WzhXFYsDanGW2G52WBkIuZ9VWaUarjrMGIS9U
gu/+NkulCWMjnBIAyuuRbguwQ8svpBbLgOtjLzuF78Unm0fN9AzS1SaTrTxr+YKj
tR+lDyXoKauglekbqjbaFDrSrQISvnCUHmyGm2L7lBwBuyPkmHEvl9j8x2vxvxhv
JPgq14qWP9zQms7080QCnyBEf1rrdbVCufGR4vXOV9hBe3aUG2M24qzAAyKzJ8IX
ZH9M+AeXzpPLFSoqjuvU6PpQUj7DBlbjZyQDSHhP8nVymQLY/fL/yTND9HhXb91E
cVLM3gxtZsQ9K+bmaU+v
=bZGB
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-08-31 Thread Gianfranco Costamagna 
- Messaggio originale -

 Da: Preston Maness aggroska...@gmail.com
 A: 721...@bugs.debian.org 721...@bugs.debian.org; 
 costamagnagianfra...@yahoo.it
 Cc: 
 Inviato: Sabato 31 Agosto 2013 4:32
 Oggetto: Re: Bug#721298: boinc-client: Idle Detection Not Working Computer 
 Always In Use
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi there,
 
 On 08/30/2013 05:59 AM, Gianfranco Costamagna wrote:
  Hi Preston,
 
  could you please try this global_prefs_override.xml file?
 
 I'm utilizing it now. I'm actually pretty impressed at how well the
 machine is still functioning even with all cores working on jobs. I
 can still browse the web, write this email, tail various logs, compiz
 effects still look nice, etc. When I tried to run everything like this
 before --Run CPU and GPU while in use, use 100 percent of resources--
 the computer became unresponsive to everything except
 Ctrl-Alt-SysRq-REISUB. I'm guessing that the RAM limits are preventing
 that from happening, as well as some of the tweaks in the init script
 in the schedule() function.
 
 However, I don't see how this tests idle detection. Is the theory that
 the scheduling tweaks negate the need to detect idle time? So far, the
 machine is still doing pretty well. I haven't checked any GPU jobs to
 see if they're getting computation errors, but the CPU jobs all seem
 to be completing just fine.
 

Ok sorry for the misunderstanding, my point was to try to enable idle detection 
starting from my xml file, nevermind, can you please try this one?

computation should start after 20 seconds of inactivity or something like that
thanks

global_preferences
   run_on_batteries0/run_on_batteries
   run_if_user_active0/run_if_user_active
   run_gpu_if_user_active0/run_gpu_if_user_active
   idle_time_to_run0.20/idle_time_to_run
   suspend_cpu_usage0.00/suspend_cpu_usage
   start_hour0.00/start_hour
   end_hour0.00/end_hour
   net_start_hour0.00/net_start_hour
   net_end_hour0.00/net_end_hour
   leave_apps_in_memory1/leave_apps_in_memory
   confirm_before_connecting0/confirm_before_connecting
   hangup_if_dialed0/hangup_if_dialed
   dont_verify_images0/dont_verify_images
   work_buf_min_days1.00/work_buf_min_days
   work_buf_additional_days10.00/work_buf_additional_days
   max_ncpus_pct100.00/max_ncpus_pct
   cpu_scheduling_period_minutes60.00/cpu_scheduling_period_minutes
   disk_interval60.00/disk_interval
   disk_max_used_gb100.00/disk_max_used_gb
   disk_max_used_pct95.00/disk_max_used_pct
   disk_min_free_gb0.00/disk_min_free_gb
   vm_max_used_pct75.00/vm_max_used_pct
   ram_max_used_busy_pct50.00/ram_max_used_busy_pct
   ram_max_used_idle_pct90.00/ram_max_used_idle_pct
   max_bytes_sec_up0.00/max_bytes_sec_up
   max_bytes_sec_down0.00/max_bytes_sec_down
   cpu_usage_limit100.00/cpu_usage_limit
   daily_xfer_limit_mb0.00/daily_xfer_limit_mb
   daily_xfer_period_days0/daily_xfer_period_days
/global_preferences


 Cheers,
 Preston Maness
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.14 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/
 
 iQEcBAEBAgAGBQJSIVWdAAoJEM8h7WmSAmad4WAH/0OeubcvbimmstM5WlRiU9J6
 noLq/lqL5MbdsqmD7vsA/sdax7GiXxkcz8x6WiQoyZkZcFQuNVWQWF8yymBxqAhi
 U8/kcBG69Kj/RHLKpBaOFpDOOHXj0WLpjKFai7CL/JrmpE93Gw8zeWPg4+wLCcjk
 xsqHOQguFbVKfQ3ujmNDnO0JnI+6bOmRnRXacRV8OhwVbH7Puf2zr0+9elfNohEf
 0glJwcWeYwsyxxrczSIImBG4GSNamR7oFanem86eTLsVowMxTBN+bOhI5Ri60yCQ
 OOdVn5tGG8g3Luk5yjDVB00UqYfiAVap/fnS/BL/+b6JeMu4SQ1BXoq/xdjonJY=
 =ilBE
 -END PGP SIGNATURE-



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-08-31 Thread Preston Maness 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Greetings,

 computation should start after 20 seconds of inactivity or
 something like that thanks

Snippet from log file:

 31-Aug-2013 03:02:40 Initialization completed 31-Aug-2013 03:02:40
 [---] Suspending computation - computer is in use

After several minutes, the logs at /var/lib/boinc-client/stdoutdae.txt
still only state that the computer is in use. Network activity
continues of course, as per the xml file with the settings. But no CPU
or GPU activity.

Is there perhaps a log of the activity that boinc is supposedly
detecting? I suspect there could be a background process of some sort
on my machine that is being detected as active user activity, leading
boinc to believe the computer is in use. But I can't find any logs
that look relevant in /var/lib/boinc-client/.

Cheers,
Preston Maness
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJSIaXqAAoJEM8h7WmSAmado74H/09vy3GeoZAJF61rerLAtHP8
1LzCPw5jzCjhopS5dVFFBDdxMl2GsvUVNFjgf+oVCXhCYUVx1Gt/0ts9HyPTO08b
zcxy6eXm+IVgO6mfgZEF/mZT2s4Uzft/IdJu3QtU11zWz3tOCnjHMZuZuwBgJ8cO
Xc4N2t2KBFUGvU1Ljl8E5NmijtGf2M8eaDejCeExqJrv//jpqenrxkbHRCieTRY2
qZonOzkGMuNTYzczdDr4pWM2L9x0G7e3j/C0OH3jk3TGAaTD6O8J04jaoiw5jkcG
+xZpyRaACOdtIticY294hGwSBAeR5jHQ/k/4mXJRudJmRvbAWaikMrihGwO3MkM=
=T+Wo
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-08-31 Thread MestreLion 
At 23:32 30/08/2013, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi there,

On 08/30/2013 05:59 AM, Gianfranco Costamagna wrote:
 Hi Preston,
 
 could you please try this global_prefs_override.xml file?

I'm utilizing it now. I'm actually pretty impressed at how well the
machine is still functioning even with all cores working on jobs. I
can still browse the web, write this email, tail various logs, compiz
effects still look nice, etc.

That's perhaps due to the VeryLow priority that boinc sets for its tasks.

Even when set to 100% CPU utilization on all cores, boinc jobs usually have
neglictible impact on overall system performance, as *any* other process that
requests CPU will, be it Firefox, compiz or tail, will take precedence over
boinc.

The same cannot be said about GPU tasks: at least with my AMD HD 7770 using
proprietary fglrx driver, some tasks run fine (einstein@home, milkyway@home)
while others make the desktop very choppy (PrimeGrid, SETI). GPU memory can
also be an issue when trying to play games with boinc GPU in use.

So I've set CPU use to 100%, always, and GPU to after computer is idle
for 3 minutes. And the machine runs really smooth, even when watching
fullscreen HD videos or playing Minecraft and games from Steam.

ML 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/debian-bugs-dist

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-08-30 Thread Gianfranco Costamagna 
Hi Preston,

could you please try this global_prefs_override.xml file?

global_preferences
   run_on_batteries0/run_on_batteries
   run_if_user_active1/run_if_user_active
   run_gpu_if_user_active1/run_gpu_if_user_active
   suspend_cpu_usage0.00/suspend_cpu_usage
   start_hour0.00/start_hour
   end_hour0.00/end_hour
   net_start_hour0.00/net_start_hour
   net_end_hour0.00/net_end_hour
   leave_apps_in_memory1/leave_apps_in_memory
   confirm_before_connecting0/confirm_before_connecting
   hangup_if_dialed0/hangup_if_dialed
   dont_verify_images0/dont_verify_images
   work_buf_min_days1.00/work_buf_min_days
   work_buf_additional_days10.00/work_buf_additional_days
   max_ncpus_pct100.00/max_ncpus_pct
   cpu_scheduling_period_minutes60.00/cpu_scheduling_period_minutes
   disk_interval60.00/disk_interval
   disk_max_used_gb100.00/disk_max_used_gb
   disk_max_used_pct95.00/disk_max_used_pct
   disk_min_free_gb0.00/disk_min_free_gb
   vm_max_used_pct75.00/vm_max_used_pct
   ram_max_used_busy_pct50.00/ram_max_used_busy_pct
   ram_max_used_idle_pct90.00/ram_max_used_idle_pct
   max_bytes_sec_up0.00/max_bytes_sec_up
   max_bytes_sec_down0.00/max_bytes_sec_down
   cpu_usage_limit100.00/cpu_usage_limit
   daily_xfer_limit_mb0.00/daily_xfer_limit_mb
   daily_xfer_period_days0/daily_xfer_period_days
/global_preferences



I see a couple of difference that may cause this issue, if it isn't a code 
problem.

thanks

Gianfranco



- Messaggio originale -
 Da: Preston Maness aggroska...@gmail.com
 A: Debian Bug Tracking System sub...@bugs.debian.org
 Cc: 
 Inviato: Venerdì 30 Agosto 2013 5:32
 Oggetto: Bug#721298: boinc-client: Idle Detection Not Working Computer Always 
 In Use
 
 Package: boinc-client
 Version: 7.2.7+dfsg-1
 Severity: important
 
 Dear Maintainer,
 
 I am unable to get BOINC to activate when computer is not in use. I
 don't know how else to troubleshoot the idle detection features of
 boinc. The log file at /var/lib/boinc-client/stdoutdae.txt simply shows
 a line that says Suspending Computation - computer is in use even
 after the idle time has been reached. The XML with the global
 configuration parameters is below.
 
 Telling boinc to run always seems to work as expected. The CPU and 
 GPU
 both get jobs at that point and start crunching away. Please advise me
 as to how I may help in further troubleshooting this issue.
 
 Cheers,
 Preston Maness
 
 -- Package-specific info:
 -- Contents of /etc/default/boinc-client:
 # This file is /etc/default/boinc-client, it is a configuration file for the
 # /etc/init.d/boinc-client init script.
 
 # Set this to 1 to enable and to 0 to disable the init script.
 ENABLED=1
 
 # Set this to 1 to enable advanced scheduling of the BOINC core client and
 # all its sub-processes (reduces the impact of BOINC on the system's
 # performance).
 SCHEDULE=1
 
 # The BOINC core client will be started with the permissions of this user.
 BOINC_USER=boinc
 
 # This is the data directory of the BOINC core client.
 BOINC_DIR=/var/lib/boinc-client
 
 # This is the location of the BOINC core client, that the init script uses.
 # If you do not want to use the client program provided by the boinc-client
 # package, you can specify here an alternative client program.
 #BOINC_CLIENT=/usr/local/bin/boinc
 BOINC_CLIENT=/usr/bin/boinc
 
 # Here you can specify additional options to pass to the BOINC core client.
 # Type 'boinc --help' or 'man boinc' for a full summary of 
 allowed options.
 #BOINC_OPTS=--allow_remote_gui_rpc
 BOINC_OPTS=
 
 # Scheduling options
 
 # Set SCHEDULE=0 if prefering to run with upstream default priority
 # settings.
 
 # Nice levels. When systems are truly busy, e.g. because of too many active
 # scientific applications started by the boinc client, there is a chance for
 # the boinc client not to be granted sufficient opportunity to check for
 # scientific applications to be alive and make the (wrong) decision to
 # terminate the scientific app. This is particularly an issue with many
 # apps started in parallel on modern multi-core systems and extra overheads
 # for the download and uploads of files with the project servers. Another
 # concern is the latency for scientific applications to communicate with the
 # graphics card, which should be low. All such values should be set and
 # controled from within the BOINC client. The Debian init script also sets
 # extra constrains via chrt on real time performance and via ionice on 
 # I/O performance, which is beyond the regular BOINC client. It then was
 # too easy to use that code to also constrain minimal nice levels. We still
 # think about how to best distinguish GPU applications from regular apps.
 BOINC_NICE_CLIENT=10
 BOINC_NICE_APP_DEFAULT=19
 #BOINC_NICE_APP_GPU=5        # not yet used
 
 # ionice classes. See manpage of ionice (1) in the util-linux package.
 BOINC_IONICE_CLIENT=3        # idle

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-08-30 Thread Preston Maness 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi there,

On 08/30/2013 05:59 AM, Gianfranco Costamagna wrote:
 Hi Preston,
 
 could you please try this global_prefs_override.xml file?

I'm utilizing it now. I'm actually pretty impressed at how well the
machine is still functioning even with all cores working on jobs. I
can still browse the web, write this email, tail various logs, compiz
effects still look nice, etc. When I tried to run everything like this
before --Run CPU and GPU while in use, use 100 percent of resources--
the computer became unresponsive to everything except
Ctrl-Alt-SysRq-REISUB. I'm guessing that the RAM limits are preventing
that from happening, as well as some of the tweaks in the init script
in the schedule() function.

However, I don't see how this tests idle detection. Is the theory that
the scheduling tweaks negate the need to detect idle time? So far, the
machine is still doing pretty well. I haven't checked any GPU jobs to
see if they're getting computation errors, but the CPU jobs all seem
to be completing just fine.

Cheers,
Preston Maness
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJSIVWdAAoJEM8h7WmSAmad4WAH/0OeubcvbimmstM5WlRiU9J6
noLq/lqL5MbdsqmD7vsA/sdax7GiXxkcz8x6WiQoyZkZcFQuNVWQWF8yymBxqAhi
U8/kcBG69Kj/RHLKpBaOFpDOOHXj0WLpjKFai7CL/JrmpE93Gw8zeWPg4+wLCcjk
xsqHOQguFbVKfQ3ujmNDnO0JnI+6bOmRnRXacRV8OhwVbH7Puf2zr0+9elfNohEf
0glJwcWeYwsyxxrczSIImBG4GSNamR7oFanem86eTLsVowMxTBN+bOhI5Ri60yCQ
OOdVn5tGG8g3Luk5yjDVB00UqYfiAVap/fnS/BL/+b6JeMu4SQ1BXoq/xdjonJY=
=ilBE
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721298: boinc-client: Idle Detection Not Working Computer Always In Use

2013-08-29 Thread Preston Maness 
Package: boinc-client
Version: 7.2.7+dfsg-1
Severity: important

Dear Maintainer,

I am unable to get BOINC to activate when computer is not in use. I
don't know how else to troubleshoot the idle detection features of
boinc. The log file at /var/lib/boinc-client/stdoutdae.txt simply shows
a line that says Suspending Computation - computer is in use even
after the idle time has been reached. The XML with the global
configuration parameters is below.

Telling boinc to run always seems to work as expected. The CPU and GPU
both get jobs at that point and start crunching away. Please advise me
as to how I may help in further troubleshooting this issue.

Cheers,
Preston Maness

-- Package-specific info:
-- Contents of /etc/default/boinc-client:
# This file is /etc/default/boinc-client, it is a configuration file for the
# /etc/init.d/boinc-client init script.

# Set this to 1 to enable and to 0 to disable the init script.
ENABLED=1

# Set this to 1 to enable advanced scheduling of the BOINC core client and
# all its sub-processes (reduces the impact of BOINC on the system's
# performance).
SCHEDULE=1

# The BOINC core client will be started with the permissions of this user.
BOINC_USER=boinc

# This is the data directory of the BOINC core client.
BOINC_DIR=/var/lib/boinc-client

# This is the location of the BOINC core client, that the init script uses.
# If you do not want to use the client program provided by the boinc-client
# package, you can specify here an alternative client program.
#BOINC_CLIENT=/usr/local/bin/boinc
BOINC_CLIENT=/usr/bin/boinc

# Here you can specify additional options to pass to the BOINC core client.
# Type 'boinc --help' or 'man boinc' for a full summary of allowed options.
#BOINC_OPTS=--allow_remote_gui_rpc
BOINC_OPTS=

# Scheduling options

# Set SCHEDULE=0 if prefering to run with upstream default priority
# settings.

# Nice levels. When systems are truly busy, e.g. because of too many active
# scientific applications started by the boinc client, there is a chance for
# the boinc client not to be granted sufficient opportunity to check for
# scientific applications to be alive and make the (wrong) decision to
# terminate the scientific app. This is particularly an issue with many
# apps started in parallel on modern multi-core systems and extra overheads
# for the download and uploads of files with the project servers. Another
# concern is the latency for scientific applications to communicate with the
# graphics card, which should be low. All such values should be set and
# controled from within the BOINC client. The Debian init script also sets
# extra constrains via chrt on real time performance and via ionice on 
# I/O performance, which is beyond the regular BOINC client. It then was
# too easy to use that code to also constrain minimal nice levels. We still
# think about how to best distinguish GPU applications from regular apps.
BOINC_NICE_CLIENT=10
BOINC_NICE_APP_DEFAULT=19
#BOINC_NICE_APP_GPU=5# not yet used

# ionice classes. See manpage of ionice (1) in the util-linux package.
BOINC_IONICE_CLIENT=3# idle
#BOINC_IONICE_APP_DEFAULT=3  # idle, not yet used
#BOINC_IONICE_APP_GPU=2  # best effort, not yet used


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages boinc-client depends on:
ii  adduser3.113+nmu3
ii  ca-certificates20130610
ii  debconf [debconf-2.0]  1.5.50
ii  libboinc7  7.2.7+dfsg-1
ii  libc6  2.17-92
ii  libcurl3   7.32.0-1
ii  libgcc11:4.8.1-2
ii  libssl1.0.01.0.1e-3
ii  libstdc++6 4.8.1-2
ii  libx11-6   2:1.6.1-1
ii  libxext6   2:1.3.2-1
ii  libxss11:1.2.2-1
ii  python 2.7.5-4
ii  zlib1g 1:1.2.8.dfsg-1

Versions of packages boinc-client recommends:
pn  ia32-libs  none

Versions of packages boinc-client suggests:
ii  boinc-manager  7.2.7+dfsg-1
pn  libcuda1   none
pn  libcuda1-ia32  none
ii  x11-xserver-utils  7.7~3

-- Configuration Files:
/etc/boinc-client/global_prefs_override.xml changed:
global_preferences
   run_on_batteries1/run_on_batteries
   run_if_user_active0/run_if_user_active
   run_gpu_if_user_active0/run_gpu_if_user_active
   idle_time_to_run2.00/idle_time_to_run
   suspend_cpu_usage25.00/suspend_cpu_usage
   start_hour0.00/start_hour
   end_hour0.00/end_hour
   net_start_hour0.00/net_start_hour
   net_end_hour0.00/net_end_hour
   leave_apps_in_memory0/leave_apps_in_memory
   confirm_before_connecting0/confirm_before_connecting
   hangup_if_dialed0/hangup_if_dialed
   dont_verify_images0/dont_verify_images