Hi,
Chris Cook wrote:
If there is no way to determine if the gconf schemas are corrupt, is
there a safe way to completely blow them away and re-install them?
Re-installing the gconf package obviously does not do this.
From the log you posted, the problem is that the gconf daemon is
exiting, so you might try just running "gconfd-2" from the command line,
or maybe under strace, and see what happens to it. (I have no guesses,
Fernando posted one.) There's also a way to make gconfd be more verbose
that I forget. (maybe HUP or USR1 or something)
For the sake of future google searchers, the way you'd replace all
schemas is:
Assuming (probably _mostly_ safe) that all packages with schemas install
the .schemas file to /etc/gconf/schemas, then you can nuke the contents
of /etc/gconf/gconf.xml.defaults and then re-create them with something
like:
export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`
for S in /etc/gconf/schemas/* ; do
gconftool-2 --makefile-install-rule $S ;
done
But, it's perhaps not for the faint of heart since your gconf-using
packages will be 100% uber-hosed without their default settings. You
might want to move /etc/gconf/gconf.xml.defaults aside rather than
deleting it.
Havoc
_______________________________________________
gconf-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gconf-list
