Hi Yordan Pavlov or jeffshantz, whilst a remote session does not allow for BOINC to detect there is activity ongoing, hands on physical should, be it mouse or keyboard and might be something to delve into indeed.

A few have reported BOINC on Linux(what distro?) to not recognise mouse activity and in fact there is a trac ticket on the topic over at the developers:

Assigned to:	davea
Milestone:	6.2
Version:	5.10.45
Cc:	fthomas

http://boinc.berkeley.edu/trac/ticket/463

By the read, the problem is targeted to be fixed in 6.2. For now, as in dire need of ram, maybe set the memory constraint for both idle and busy at a very low percent so that at least BOINC stops if something else is demanding the use of it and it only runs when your work programs are not loaded. BOINC will run slower as it will have to swap more often with disc, so my recommendation here would be to pick the smallest WCG projects which are HCC & HPF2. The upcoming new project might also be small, but did not pay attention during the beta test as to how much it uses.

Here's the present list by order of smallness:

1. HCC (10 days)
2. HPF2 (20 days)
3. FA@H (10 days)
4. DDDT (14 days)
5. AC@H (10days)

You are of course always welcome to be vocal.

However, if you have C/C++ skills then the BOINC project would always appreciate volunteers who are able to get into the code and provide some useful, well written improvements. Start off by starting to monitor some of the BOINC mailing lists, downloading the source and building the client yourself and taking a look at the code for the feature you want to change.