Cannot load GNOME under Sarge

2004-01-15 Thread Jim Seymour
Hi All, Still have not been able to run GNOME on Sarge. If I try to boot into GNOME I get a very brief view of a splash screen and then a small window pops up in the corner of the screen with the following message: "There was an error starting the GNOME Settings Daemon." "Some things, s

Re: Cannot load GNOME under Sarge

2004-01-15 Thread Jim Seymour
On Thu, Jan 15, 2004 at 11:38:00AM -0500, mukesh agrawal wrote: > On Thu, 15 Jan 2004, Jim Seymour wrote: > > > Hi All, > > Still have not been able to run GNOME on Sarge. If I try to boot > > into GNOME I get a very brief view of a splash screen and then a small > > window pops up in the corn

Re: Cannot load GNOME under Sarge

2004-01-15 Thread Jim Seymour
On Thu, Jan 15, 2004 at 01:05:08PM -0500, mukesh agrawal wrote: > On Thu, 15 Jan 2004, Jim Seymour wrote: > > > 1. I can ping the loopback device fine. > > > > 2. I moved the .gnome* and .gconf* files to another directory. Same > > results as before and same message :-( > > > > Any other ideas? >

Re: Cannot load GNOME under Sarge

2004-01-15 Thread mukesh agrawal
On Thu, 15 Jan 2004, Jim Seymour wrote: > Hi All, > Still have not been able to run GNOME on Sarge. If I try to boot > into GNOME I get a very brief view of a splash screen and then a small > window pops up in the corner of the screen with the following message: > > "There was an error start

Re: Cannot load GNOME under Sarge

2004-01-15 Thread Jim Seymour
On Thu, Jan 15, 2004 at 05:49:09PM -0800, Theodore Reed wrote: > I don't suppose you've tried rebooting? I've seen similar messages > before, which seem to be related to bonobo/CORBA, and are fixed by > rebooting. Oh yeah.many reboots while trying to log into GNOME :-) It is the only way I kn

Re: Cannot load GNOME under Sarge

2004-01-15 Thread mukesh agrawal
On Thu, 15 Jan 2004, Jim Seymour wrote: > 1. I can ping the loopback device fine. > > 2. I moved the .gnome* and .gconf* files to another directory. Same > results as before and same message :-( > > Any other ideas? Two other ideas: 1. Check your .xsession-errors file to see if there is a more i