On Wed, Oct 15, 2008 at 2:45 AM, Per Lönnborg <[EMAIL PROTECTED]> wrote: > I have tried both. (removing hidden files and so on) Same error. > > FYI this sunray-server has an uptime of 477 days. There´s plenty of users of > this system so I rather not like to reboot it. This login error occured 2 > days ago. > > I also created a completely new account with no files at all in that users > home-directory. Same error. > It does create the .gnome, .gnome2, .gnome2_private (and the .Xauthority, > .dt, .dtprofile dirs as well) in the users homedirectory.
What do this new user's ~/.dt/errorlog and ~/.dt/startlog files contain? > Can the gconfd be restarted without affect all the logged in users? Every Gnome (JDS) session gets its own gconfd. It gets started on demand, whenever an application tries to access Gnome configuration information and a gconfd is not already running in that session. You don't have to worry about manually restarting it. If you can find the core file that gconfd says it left behind then you could run 'pstack' on the file. That'll tell you what gconfd was trying to do when it failed. If you post the 'pstack' result then somebody can check it against known bug reports. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
