Gnome-settings-daemon problem under gnome 2.18

[Volker]

On 12/23/-58 20:59, Trigve Siver wrote:
> Hi
> I have update gnome to gnome 2.18. I'm using FreeBSD 6.2 with Xorg 7.2 with X11BASE set to /usr/local. When I try to log in gnome the message window with this message popup:
> 
> There was an error starting the GNOME Settings Daemon.
> 
> Some things, such as themes, sounds, or background settings may not work correctly.
> 
> The last error message was:
> 
> Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy
>  blocked the reply, the reply timeout expired, or the network connection was broken.
> 
> GNOME will still try to restart the Settings Daemon next time you log in.
> 
> output from /var/log/messages:
> 
> Apr 18 12:17:33 pentium4 seahorse-agent[1677]: DNS-SD initialization failed: Dae
> mon not running
> Apr 18 12:17:33 pentium4 seahorse-agent[1677]: Failed to send buffer
> Apr 18 12:17:33 pentium4 seahorse-agent[1677]: Failed to send buffer 
> 
> Once I'm logged in, desktop is useless because there are no icons on panel and I can do nothing.
> When I logged in as a root, the message still appears
>  but icons on the panel are ok and I can use it.
> 
> Anyone know where could be the problem?
> 
> thanks
> 
> Trigve

Trigve,

if you googled a bit for that, I've had the exactly same error
message in February but didn't get a reply. Some ubuntu users were
also having this but they judged that being a software bug.

I've been able to solve that problem by deleting most user specific
gnome configuration settings (~/.g*/*, ~/.nautilus*/* etc.). You may
verify it's a local user configuration problem by adding a fresh
user to your system and log in from gdm and not seeing this problem.

If you can make sure this problem doesn't pop up using a fresh user
configuration, drop your old user config and this problem should
disappear. Also check your session settings.

Your DNS-SD problem with 'Failed to send buffer' seems to be a
different story. You should check network settings at the first place.

HTH,

Volker