How about trying this script:

#!/bin/bash
# Reset GNOME schemas to default values

for i in /etc/gconf/schemas/* ; do
GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source` gconftool-2 --makefile-install-rule $i > /dev/null
done

Originally posted by mhelios
How about trying this script:

#!/bin/bash
# Reset GNOME schemas to default values

for i in /etc/gconf/schemas/* ; do
GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source` gconftool-2 --makefile-install-rule $i > /dev/null
done


i tried it: got this output
WARNING: no <list_type> specified for schema of type list
WARNING: failed to install schema `/schemas/desktop/standard/recent-document-entry' locale `C': Schema specifies type list but doesn't specify the type of the list elements
WARNING: no <car_type> specified for schema of type pair
WARNING: no <cdr_type> specified for schema of type pair
WARNING: failed to install schema `/schemas/desktop/standard/save-location-entry' locale `C': Schema specifies type pair but doesn't specify the type of the car/cdr elements
Document `/etc/gconf/schemas/panel-default-setup-battstat.entries' has the wrong type of root node (<gconfentryfile>, should be <gconfschemafile>)
Document `/etc/gconf/schemas/panel-default-setup.entries' has the wrong type of root node (<gconfentryfile>, should be <gconfschemafile>)

and still doesnt work, i gethe same error. Thanks for the help though....

deech

deech, this bug is already in Bugzilla, but unfortunately, there's no resolution for it yet. Could you please add your details to the following bug report, mentioning what OS release it's triggered the bug in (FC2t3).

http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112467

Hm. I suppose the obvious; that metacity is installed, right? Yea, of course it is. :o

Well, the 105 updates must have included soem gnome-* packages, no? I would suggest either:

a) downgrade these updated gnome packages for now

b) put up with it and just wait for FC2 final next week. :D

a) would probably solve your problem but is not worth it since it's a test release after all..
b) is probably more practical since this problem *should* not be there for the final release.

i think i ll go for plan b. Dont have time to dig deeper into this, and you're right, it should be no problem in the final FC2.

Thanx again anyway,

greetings from holland ;)

deech