Re: schema troubles

["Fernando Herrera" <fherrera onirica com>]

Hi,

check your file:
/etc/gconf/2/path

it should contains lines like this:
xml:readonly:/etc/gconf/gconf.xml.mandatory
xml:readonly:/etc/gconf/gconf.xml.defaults

but if you have something like this:
xml:readonly:${prefix}/gconf/gconf.xml.mandatory
xml:readonly:${prefix}/gconf/gconf.xml.defaults

that it's a known bug on gconf, fixed on the latest version.

Salu2


On 5/25/06, Chris Cook <beerfan gmail com> wrote:
> I think my gconf schemas may have become corrupt.
>
> When I try to run gnome-theme-manager I get an error dialog which says
> "The default theme schemas could not be found on your system. This
> means that you probably don't have metacity installed, or that your
> gconf is configured incorrectly." Other gnome control center managers
> (like keyboard properties) crash with a generic error when run and
> others (like mouse properties) don't save changes. Furthermore, mouse
> and keyboard default settings seem to have changed (keypress repeat no
> longer works and mouse acceleration is super fast).
>
> I've read over the troubleshooting techniques on
> http://www.gnome.org/projects/gconf/ but can't find anything that
> tells me what's wrong.
>
> Here is some syslog from trying to run gnome-theme-manager.
> --------
> May 25 01:21:32 localhost gconfd (tangent-8200): starting (version
> 2.14.0), pid 8200 user 'tangent'
> May 25 01:21:32 localhost gconfd (tangent-8200): Resolved address
> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
> configuration source at position 0
> May 25 01:21:32 localhost gconfd (tangent-8200): Resolved address
> "xml:readwrite:/home/tangent/.gconf" to a writable configuration
> source at position 1
> May 25 01:21:32 localhost gconfd (tangent-8200): Resolved address
> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
> configuration source at position 2
> May 25 01:21:32 localhost gconfd (tangent-8200): Resolved address
> "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only
> configuration source at position 3
> May 25 01:21:32 localhost gconfd (tangent-8200): Resolved address
> "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration
> source at position 4
> May 25 01:25:35 localhost gconfd (tangent-8200): Exiting
> May 25 01:25:50 localhost gconfd (tangent-8317): starting (version
> 2.14.0), pid 8317 user 'tangent'
> May 25 01:25:50 localhost gconfd (tangent-8317): Resolved address
> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
> configuration source at position 0
> May 25 01:25:50 localhost gconfd (tangent-8317): Resolved address
> "xml:readwrite:/home/tangent/.gconf" to a writable configuration
> source at position 1
> May 25 01:25:50 localhost gconfd (tangent-8317): Resolved address
> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
> configuration source at position 2
> May 25 01:25:50 localhost gconfd (tangent-8317): Resolved address
> "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only
> configuration source at position 3
> May 25 01:25:50 localhost gconfd (tangent-8317): Resolved address
> "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration
> source at position 4
> -------
>
> I'm using Ubuntu dapper with gconf 2.14.0 installed. I've tried
> reinstalling gconf, gnome control center, and metacity. I've also
> tried removing ~/.gconf with no effect.
>
> Can anyone tell me how to verify if the schemas are corrupt or how to
> proceed with fixing this?
>
> Cheers
> _______________________________________________
> gconf-list mailing list
> gconf-list gnome org
> http://mail.gnome.org/mailman/listinfo/gconf-list