--- Begin Message ---
Package: gfax
Version: 0.7.6-7
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080308 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Relevant part:
> make[3]: Entering directory `/build/user/gfax-0.7.6/src'
> sed -e "s|[EMAIL PROTECTED]@|0.7.6|" \
> -e "s|[EMAIL PROTECTED]@|/usr/share|" \
> -e "s|[EMAIL PROTECTED]@||" \
> < Defines.cs.in > Defines.cs
> make[3]: Circular Settings.cs <- Settings.cs dependency dropped.
> env GCONF_CONFIG_SOURCE="" gconftool-2 --makefile-install-rule
> ../gfax.schemas.in; \
> gconfsharp2-schemagen gfax ../gfax.schemas.in > ./Settings.cs
> Attached schema `/schemas/apps/gfax/general/refresh_queue_interval' to key
> `/apps/gfax/general/refresh_queue_interval'
> WARNING: failed to install schema
> `/schemas/apps/gfax/general/refresh_queue_interval' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/general/refresh_queue_interval', 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
> Attached schema `/schemas/apps/gfax/general/run_setup_at_start' to key
> `/apps/gfax/general/run_setup_at_start'
> WARNING: failed to install schema
> `/schemas/apps/gfax/general/run_setup_at_start' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/general/run_setup_at_start', 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
> Attached schema `/schemas/apps/gfax/general/log_enabled' to key
> `/apps/gfax/general/log_enabled'
> WARNING: failed to install schema `/schemas/apps/gfax/general/log_enabled'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/log_enabled', 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
> Attached schema `/schemas/apps/gfax/general/refresh_queue_enabled' to key
> `/apps/gfax/general/refresh_queue_enabled'
> WARNING: failed to install schema
> `/schemas/apps/gfax/general/refresh_queue_enabled' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/general/refresh_queue_enabled', 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
> Attached schema `/schemas/apps/gfax/general/send_now' to key
> `/apps/gfax/general/send_now'
> WARNING: failed to install schema `/schemas/apps/gfax/general/send_now'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/send_now', 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
> Attached schema `/schemas/apps/gfax/general/email_notify' to key
> `/apps/gfax/general/email_notify'
> WARNING: failed to install schema `/schemas/apps/gfax/general/email_notify'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/email_notify', 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
> Attached schema `/schemas/apps/gfax/general/cover_page' to key
> `/apps/gfax/general/cover_page'
> WARNING: failed to install schema `/schemas/apps/gfax/general/cover_page'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/cover_page', 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
> Attached schema `/schemas/apps/gfax/general/hi_resolution' to key
> `/apps/gfax/general/hi_resolution'
> WARNING: failed to install schema `/schemas/apps/gfax/general/hi_resolution'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/hi_resolution', 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
> Attached schema `/schemas/apps/gfax/general/phone_prefix' to key
> `/apps/gfax/general/phone_prefix'
> WARNING: failed to install schema `/schemas/apps/gfax/general/phone_prefix'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/phone_prefix', 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
> Attached schema `/schemas/apps/gfax/general/fax_number' to key
> `/apps/gfax/general/fax_number'
> WARNING: failed to install schema `/schemas/apps/gfax/general/fax_number'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/fax_number', 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
> Attached schema `/schemas/apps/gfax/general/email_address' to key
> `/apps/gfax/general/email_address'
> WARNING: failed to install schema `/schemas/apps/gfax/general/email_address'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/email_address', 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
> Attached schema `/schemas/apps/gfax/general/transmit_agent' to key
> `/apps/gfax/general/transmit_agent'
> WARNING: failed to install schema `/schemas/apps/gfax/general/transmit_agent'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/transmit_agent', 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
> Attached schema `/schemas/apps/gfax/general/fax_viewer' to key
> `/apps/gfax/general/fax_viewer'
> WARNING: failed to install schema `/schemas/apps/gfax/general/fax_viewer'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/general/fax_viewer', 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
> Attached schema `/schemas/apps/gfax/transport/hylafax/hostname' to key
> `/apps/gfax/transport/hylafax/hostname'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/hylafax/hostname' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/hylafax/hostname', 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
> Attached schema `/schemas/apps/gfax/transport/hylafax/port' to key
> `/apps/gfax/transport/hylafax/port'
> WARNING: failed to install schema `/schemas/apps/gfax/transport/hylafax/port'
> locale `C': No database available to save your configuration: Unable to store
> a value at key '/schemas/apps/gfax/transport/hylafax/port', 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
> Attached schema `/schemas/apps/gfax/transport/hylafax/username' to key
> `/apps/gfax/transport/hylafax/username'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/hylafax/username' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/hylafax/username', 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
> Attached schema `/schemas/apps/gfax/transport/hylafax/password' to key
> `/apps/gfax/transport/hylafax/password'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/hylafax/password' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/hylafax/password', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_device' to key
> `/apps/gfax/transport/efax/efax_modem_device'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_device' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_device', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_init' to key
> `/apps/gfax/transport/efax/efax_modem_init'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_init' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_init', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_fcinit' to key
> `/apps/gfax/transport/efax/efax_modem_fcinit'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_fcinit' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_fcinit', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_reset' to key
> `/apps/gfax/transport/efax/efax_modem_reset'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_reset' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_reset', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_speaker_mode'
> to key `/apps/gfax/transport/efax/efax_modem_speaker_mode'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_speaker_mode' locale `C': No
> database available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_speaker_mode', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_speaker_volume'
> to key `/apps/gfax/transport/efax/efax_modem_speaker_volume'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_speaker_volume' locale `C': No
> database available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_speaker_volume', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_class' to key
> `/apps/gfax/transport/efax/efax_modem_class'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_class' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_class', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_modem_capabilities'
> to key `/apps/gfax/transport/efax/efax_modem_capabilities'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_modem_capabilities' locale `C': No
> database available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_modem_capabilities', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_lockfile' to key
> `/apps/gfax/transport/efax/efax_lockfile'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_lockfile' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_lockfile', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_page_header' to key
> `/apps/gfax/transport/efax/efax_page_header'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_page_header' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_page_header', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_retries' to key
> `/apps/gfax/transport/efax/efax_retries'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_retries' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_retries', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_next_jobid' to key
> `/apps/gfax/transport/efax/efax_next_jobid'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_next_jobid' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_next_jobid', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_papersize' to key
> `/apps/gfax/transport/efax/efax_papersize'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_papersize' locale `C': No database
> available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_papersize', 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
> Attached schema `/schemas/apps/gfax/transport/efax/efax_debug_messages' to
> key `/apps/gfax/transport/efax/efax_debug_messages'
> WARNING: failed to install schema
> `/schemas/apps/gfax/transport/efax/efax_debug_messages' locale `C': No
> database available to save your configuration: Unable to store a value at key
> '/schemas/apps/gfax/transport/efax/efax_debug_messages', as the configuration
> server has no writable databases. There are some common causes of this
> problumount:
> /tmp/schroot/mount/sid32-097fc80e-6927-486b-9bae-543586b6f534/tmp: device is
> busy
> umount: /tmp/schroot/mount/sid32-097fc80e-6927-486b-9bae-543586b6f534/tmp:
> device is busy
> E: sid32-097fc80e-6927-486b-9bae-543586b6f534: Chroot setup failed:
> stage=setup-stop
> Chroot cleanup failed
> em: 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
> mcs -nowarn:0169,0219 -debug
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glib-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/pango-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/atk-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gdk-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gtk-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gnome-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/art-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gnome-vfs-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gconf-sharp.dll
> -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glade-sharp.dll
> -r:/usr/lib/cli/evolution-sharp-3.0/evolution-sharp.dll -r:Mono.Posix
> -resource:../glade/gfax.glade,gfax.glade
> -resource:../glade/send-druid.glade,send-druid.glade
> -resource:../pixmaps/gfax.png,gfax.png
> -resource:../pixmaps/send.png,send.png efax.cs fax.cs
> gui.cs gfaxprefs.cs gfaxsend.cs gfaxphonebook.cs
> newphonebook.cs guitools.cs hylafax.cs
> main.cs phonebook.cs evolution.cs
> sendphonebook.cs Defines.cs Settings.cs -o gfax.exe
> warning CS8029: Compatibility: Use -out:FILE instead of --output FILE or -o
> FILE
> gui.cs(28,15): error CS0234: The type or namespace name `PropertyEditors'
> does not exist in the namespace `GConf'. Are you missing an assembly
> reference?
> gui.cs(28,9): error CS0246: The type or namespace name
> `GConf.PropertyEditors' could not be found. Are you missing a using directive
> or an assembly reference?
> Compilation failed: 2 error(s), 1 warnings
> make[3]: *** [gfax.exe] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/03/08
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
