On Wed, 2005-08-31 at 13:50 +0200, Jules Colding wrote:
> On Wed, 2005-08-31 at 12:14 +0200, Jules Colding wrote:
> > > Make sure you don't use 2.3.8, it has a bug in one of the eds libraries
> > > which causes strange crashes in things like gstrdupprintf.
> >
> > I updated from CVS, but to no avail as seen below. I am completely
> > baffled as to how I can get my Evolution build up and running and any
> > ideas would be very much appreciated.
>
> Could my problems have something to do with schema installation and
> gconf? Evolution puts the 2.4 schemas in "~/opt/etc/gconf/schemas" but
> gconf might only see the global "/etc/gconf/schemas" directory
> (containing the Evolution 2.2 schemas)?
It at least seems to be related. I am getting a whole bunch of warnings
about the build not being able to install any schemas. Any idea on how I
make the schema installation succeed?
Thanks,
jules
########### A few of the schema installation warnings ###############
----------------------------------------------------------------------
if test -z ""; then \
for p in apps_evolution_calendar-2.4.schemas; do \
GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults
/usr/bin/gconftool-2 --makefile-install-rule $p; \
done; \
fi
Resolved address "xml::/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 0
None of the resolved addresses are writable; saving configuration settings will
not be possible
Attached schema `/schemas/apps/evolution/calendar/display/timezone' to key
`/apps/evolution/calendar/display/timezone'
WARNING: failed to install schema
`/schemas/apps/evolution/calendar/display/timezone' locale `th': Can't
overwrite existing read-only value: Value for
`/schemas/apps/evolution/calendar/display/timezone' set in a read-only source
at the front of your configuration path
----------------------------------------------------------------------
if test -z "" ; then \
for p in evolution-mail-2.4.schemas ; do \
GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults
/usr/bin/gconftool-2 --makefile-install-rule $p; \
done \
fi
Resolved address "xml::/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 0
None of the resolved addresses are writable; saving configuration settings will
not be possible
Attached schema `/schemas/apps/evolution/mail/composer/charset' to key
`/apps/evolution/mail/composer/charset'
WARNING: failed to install schema
`/schemas/apps/evolution/mail/composer/charset' locale `cs': Can't overwrite
existing read-only value: Value for
`/schemas/apps/evolution/mail/composer/charset' set in a read-only source at
the front of your configuration path
WARNING: failed to install schema
`/schemas/apps/evolution/mail/composer/charset' locale `nl': Can't overwrite
existing read-only value: Value for
`/schemas/apps/evolution/mail/composer/charset' set in a read-only source at
the front of your configuration path
-----------------------------------------
Making install in default-mailer
make[2]: Entering directory
`/home/evo/work/src/evolution/plugins/default-mailer'
make[3]: Entering directory
`/home/evo/work/src/evolution/plugins/default-mailer'
make[3]: Nothing to be done for `install-exec-am'.
if test -z "" ; then
\
for p in apps-evolution-mail-prompts-checkdefault-2.4.schemas ; do
\
GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults
/usr/bin/gconftool-2 --makefile-install-rule $p; \
done
\
fi
Resolved address "xml::/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 0
None of the resolved addresses are writable; saving configuration settings will
not be possible
Attached schema `/schemas/apps/evolution/mail/prompts/checkdefault' to key
`/apps/evolution/mail/prompts/checkdefault'
WARNING: failed to install schema
`/schemas/apps/evolution/mail/prompts/checkdefault' locale `th': Unable to
store a value at key '/schemas/apps/evolution/mail/prompts/checkdefault', as
the configuration server has no writable databases. There are some common
causes of this problem: 1) your configuration path file /etc/gconf/2/path
doesn't contain any databases or wasn't found 2) somehow we mistakenly created
two gconfd processes 3) your operating system is misconfigured so NFS file
locking doesn't work in your home directory or 4) your NFS client machine
crashed and didn't properly notify the server on reboot that file locks should
be dropped. If you have two gconfd processes (or had two at the time the second
was launched), logging out, killing all copies of gconfd, and logging back in
may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem
is that you attempted to use GConf from two machines at once, and ORBit still
has its default configuration that prevents remote CORBA connections - put
"ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details
on problems gconfd encountered. There can only be one gconfd per home
directory, and it must own a lockfile in ~/.gconfd and also lockfiles in
individual storage locations such as ~/.gconf
_______________________________________________
Evolution-hackers mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/evolution-hackers
