Re: gnome (gconf) saga - please read

Elliot Lee <sopwith redhat com> writes:
> When the gconfd dies mysteriously (e.g. you kill the session it is part
> of), the XML backend leaves a lock directory that you just need to remove
> - ~/.gconf/%gconf-xml-backend.lock

This is no longer the case, because now kernel locks are used instead
of bogus userspace locks. So on when gconfd dies the locks are cleaned
up. It's quite robust - unless the kernel crashes and the OS has 
a bug in it. :-/

The RH bug btw is:

> The funky flailing you did is probably what caused the loss of settings,
> not any gconf design problems.

It is possible to lose settings if you pull the power cord, because 
gconfd keeps "write buffers" - however you should never lose more than
a couple minutes worth of settings.

Ctrl+Alt+Backspace should not kill gconfd, though, since gconfd isn't
connected to X.

The panel (in 1.0) has a tendency to lose settings on
Ctrl+Alt+Backspace, but it isn't using GConf. I'm not sure what the
issue is there.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]