<mark_weaver>yeah, the test-async-cancel test in gnome-vfs sporadically fails, and not just for us. it's a known problem, but that module is deprecated and the problem will apparently never be fixed upstream.
<mark_weaver>for months, I've been manually restarting those builds until the test passes, but I've had enough of that
<mark_weaver>during 'make install', there are a large number of these warnings in gnome-vfs:
<mark_weaver>WARNING: failed to install schema `/schemas/system/http_proxy/port', locale `eo': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/3j7099a1yabpmpk8kpc5i9k235k34abp-gconf-3.2.6/etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two
<mark_weaver>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
<mark_weaver>~/.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