error starting g-s-d on systems with low memory

Thanks for taking your time to report this bug and helping to make Ubuntu better.

Can you please provide your ~/.xsession-errors from a failed attempt to start the settings daemon as well as the output from "gnome-settings-daemon --debug"?
Also, please provide the version of gnome-settings-daemon you're using (you can see that by entering "apt-cache policy gnome-settings-daemon" without the quotes in a terminal)

Thanks,

Here you are. The information you asked is at the end of xsession-errors.
Please note that I did find gnome-settings-daemon started.
And that if I kill it, it will restart automatically.
I found no better way than to "kill -9; gnome-settings-daemon"
First time I did this, my session was killed, maybe my mistake.
Later, I received a message saying that g-s-d had restarted too many times.
In the confusion, I forgot --debug :-(

Tell me if you find what you need.
Else, what exactly I must do to help.

Thanks too for the marvelous job you do.

The xsession-errors file does not contain any sign of gnome-settings-daemon failing. Did you receive the error dialog you posted above this time? If not, could you please give us the .xsession-errors from a failed attempt?

Thanks,

On 2008-03-29 14:49, Kjell Braden wrote :
> The xsession-errors file does not contain any sign of gnome-settings-
> daemon failing. Did you receive the error dialog you posted above this
> time?
The error dialog appeared after I booted the Live CD, when the ubuntu
user logged in.
I suppose that's the way the data you're looking for should have been
logged to that file.
Regarding the other, painful attempts to stop/start
gnome-settings-daemon anew, no, I haven't seen a message in these cases.

I imagine that the message is issued by some too impatient ("Timeout
likely, 400 MHZ") code wanting to use the daemon and receiving no prompt
reply in the case of a slow CD-based startup.
So, beyond one missed request if that's true, the only consequence is
the "Ugly to see in a demo".

You should indeed imagine a party commenting about the slowness of CDs
while watching the long-lasting brown, blank screen, saying "ah" when a
white rectangle draws in the top left corner, and saying "oh" quite a
number of seconds later when the first sign of intelligence they receive
is an error message.

If raising a time-out can avoid that, it'll be well spent time.

Now that we're at 8.04 CR...
FYI, this is the ugly Ubuntu welcome I'm trying to avoid...
at the expense of something like raising some timeout.

could you try if that's still an issue in jaunty?

On 2009-04-22 00:27, Sebastien Bacher wrote :
> could you try if that's still an issue in jaunty?
>
It seems that somebody noticed and fixed the problem, 1 year later.
Thanks to him if we ever know who.
Thank you too.

closing the bug since that works now