Version: 2.22.3

What were you doing when the application crashed?



Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.3 2008-07-09 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors ---------------------

+ Trace 212326

Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/glchess/gtkui/dialogs.py", line 671, in _on_show_history_activate
    glchess.config.set('show_history', widget.get_active())
  File "/var/lib/python-support/python2.5/glchess/config.py", line 145, in set
    function(_GCONF_DIR + name, value)
GError: No database available to save your configuration: Unable to store a value at key '/apps/glchess/show_history', as the configuration server has no writable databases. There are some common caus
--------------------------------------------------
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/glchess/gtkui/dialogs.py", line 671, in _on_show_history_activate
    glchess.config.set('show_history', widget.get_active())
  File "/var/lib/python-support/python2.5/glchess/config.py", line 145, in set
    function(_GCONF_DIR + name, value)
GError: No database available to save your configuration: Unable to store a value at key '/apps/glchess/show_history', 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