I've set up my client to only run when idle, yet it ignores this. I know that some people had previously had a problem with the client not detecting mouse use, but as I sit here typing this, running applications left and right, top shows two instances of setiathome-5.12 using 100% cpu each (dual core cpu).

idle_time_to_run is set to 15 in global_prefs.xml, and run_if_user_active is set to 0 in global_prefs_override.xml. I've seen that a few people have had issues with the client NOT running when it should, but I'm having the exact opposite problem. Any suggestions?

What distro of linux are you using? And what is your BOINC version?

Also, if you have BOINC version 5.10 or higher, be sure you don't have any override preferences in the advanced menu.

What distro of linux are you using? And what is your BOINC version?

Also, if you have BOINC version 5.10 or higher, be sure you don't have any override preferences in the advanced menu.

I'm running Debian Sid on AMD64. Though, oddly enough, since I rebooted earlier it's worked fine. What's strange is that I had restarted the service a number of times earlier while testing, so I'm not sure what changed during the reboot (same kernel and everything, no major changes) but it suddenly started picking up user activity correctly.

So problem solved I guess, though I have no idea why.

What distro of linux are you using? And what is your BOINC version?

Also, if you have BOINC version 5.10 or higher, be sure you don't have any override preferences in the advanced menu.

I'm running Debian Sid on AMD64. Though, oddly enough, since I rebooted earlier it's worked fine. What's strange is that I had restarted the service a number of times earlier while testing, so I'm not sure what changed during the reboot (same kernel and everything, no major changes) but it suddenly started picking up user activity correctly.

So problem solved I guess, though I have no idea why.

Maybe a buggy X server? If you have any security patches/bug fixes for your distro, as good maintenance, you could install those. Otherwise, if this happens again, try logging out and back in (restarting X).