Everything d/l and installs until time to run boinc. Boinc icon will deploy to screen and can be opened in gui. I worked it from command line using both sudo as root and with my own username. Request guidance.

Here is an example of what I see on terminal;

dave@The-Mighty-Wurlitzer:~$ sudo kboincspy URL http://setiathome.berkeley.edu
Error: "/var/tmp/kdecache-dave" is owned by uid 1000 instead of uid 0.
Plugin LHC@home Monitor for project lhcathome.cern.ch loaded successfully
Plugin Einstein@home Monitor for project einstein.phys.uwm.edu loaded successfully
Plugin AstroPulse Monitor for project setiboinc.ssl.berkeley.edu_ap loaded successfully
Plugin SETI@home Monitor for project setiathome.berkeley.edu loaded successfully
Plugin SETI@home Monitor for project setiathome.ssl.berkeley.edu loaded successfully
Plugin SETI@home Monitor for project setiweb.ssl.berkeley.edu loaded successfully
Plugin ProteinPredictorAtHome Monitor for project predictor.scripps.edu loaded successfully
Plugin ProteinPredictorAtHome Monitor for project predictor1.scripps.edu loaded successfully
Plugin ClimatePrediction.net Monitor for project www.climateprediction.net loaded successfully
Plugin ClimatePrediction.net Monitor for project climateprediction.net loaded successfully
dave@The-Mighty-Wurlitzer:~$ client = boinc
Error: "/tmp/ksocket-dave" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-dave" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-dave" is owned by uid 1000 instead of uid 0.

chmod 0 is ineffective since the /tmp file is evidently recreated and rewritten each time boinc attempts to start.

Ideas?

Does any of this help?

kboincspy != BOINC

It's an alternative manager. One that I've not tried on KDE4. I wasn't all that impressed with it on KDE3.

What happens when you use the manager from Berkeley? What are you doing with this line?

`dave@The-Mighty-Wurlitzer:~$ client = boinc`

---

Kathryn :o)

What are you doing with this line?

`dave@The-Mighty-Wurlitzer:~$ client = boinc`

I think that's kboincspy still printing stuff after the shell already printed its prompt.

---