I installed the BOINC client and BOINC manager a few days ago, and everything seems to work just fine except one niggling error: I've set the options so that BOINC suspends itself when the computer has been "in use" sometime in the last 15 minutes, "in use" meaning mouse and keyboard movements.

Now, the detection of my keyboard (a wired Keytronic Ergoforce) works just fine, but the detection of my mouse (a wireless Logitech something-something) does not work. This means that I could be doing something for 15 minutes using only the mouse, when suddenly BOINC kicks in and devours my CPU until I press any key on the keyboard. How rude! Annoying, too.

This might possibly be related to this guy's problem with his wireless keyboard and mouse in Vista:
http://boinc.berkeley.edu/dev/forum_thread.php?id=2538
He fixed it by installing the manufacturer's drivers for his keyboard and mouse, but there is no such thing for Linux.

For the record, I'm using the 5.10.8 versions of the BOINC client and manager. My Ubuntu Linux version is 7.10.

Hi, Erlend. Welcome to BOINC forums.

AFAIK, the intended behavior is that selecting "Run always" under Activity overrides an unchecked "While computer is in use" so make sure you have "Run based on preferences" selected in addition to clearing the "While computer is in use" box.

Testing on my BOINC 5.10.45 installed on 32-bit Fedora 8 as well as 64-bit Fedora 7, neither mouse use nor keyboard use cause BOINC to suspend. I've tried wireless keyboard + wireless mouse as well as wired mouse and keyboard. Neither restarting BOINC nor rebooting help.

Is this a bug in BOINC or a bug/deficiency/difference in Linux mouse/keyboard drivers?

Read the saga at trac ticket [trac]#463[/trac]!

I'll reopen the ticket, if need be.

---

If he wants to close it again, he can. Not as fixed though when it's not fixed.
I increased the milestone to 6.2, just in case.

If anyone wants to add a comment there, Trac needs separate registration to read and add to tickets.

---

Well, it's nice to see the problem is already being worked on. As I mentioned, my keyboard detection seems to be working fine, so the fact that the mouse detection isn't working is more of an annoyance than a real problem. I'd still love to see it fixed, though.