Boinc fails to reopen current projects (9.10)

[Blempis]

Binary package hint: boinc

At first everything seems normal. Boinc is checking the system's status. After minute or two boinc gives it's error message but no further information is included. Current projects are not shown and new ones cannot be added. This problem occurs when computer was shut down for awhile.

There seems to be a work around to solve the problem. Just reinstall boinc with synaptic - every time. However, this is not a satisfying method.

My system: 64 bit U910 (Karmic)

ProblemType: Bug
Architecture: amd64
Date: Sat Mar 6 08:48:42 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: boinc 6.4.5+dfsg-2ubuntu2
ProcEnviron:
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
SourcePackage: boinc
Uname: Linux 2.6.31-20-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1481): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1481): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1526): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1565): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:1974): GLib-WARNING **: g_set_prgname() called multiple times

[KevinM (kevbert1)]

This also occurs in Lucid 10.04 kernel 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux.
In .xsession-errors I get
execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!
execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!
as well as the polkit errors.
I get no Projects displayed (even though I should have approx 8 attached), see attachment.

[Daniel Hahler (blueyed)]

I've marked this as duplicate of bug 608058 - which is apparently the same.
Please un-dupe, if I'm wrong.

[Daniel Hahler (blueyed)]

Blempis, please check if you have the same entries in ~/.xsession-errors - I've marked it primarily as duplicate, because I thought it was an earlier bug reported by Kevin.