After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 558268 - crash in Chess: winning
crash in Chess: winning
Status: RESOLVED DUPLICATE of bug 546694
Product: gnome-games-superseded
Classification: Deprecated
Component: glchess
2.22.x
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-28 16:50 UTC by sawclub
Modified: 2008-10-28 22:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description sawclub 2008-10-28 16:50:15 UTC 
Version: 2.22.3

What were you doing when the application crashed?
winning


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 ---------------------
Traceback (most recent call last):

+ Trace 208832

  • 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 
Unable to make data directory /home/customer/.gnome2/glchess/: Permission denied
Traceback (most recent call last):

+ Trace 208832

  • 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):

+ Trace 208832

  • 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 
es 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
Comment 1 Susana 2008-10-28 22:22:21 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 546694 ***